Resync the vendored backend types - #241
Merged
Merged
Conversation
The drift gate compares shard_core/data_model/backend against freeshard-controller main byte for byte, and it is red on every PR opened against current main (#173 and #240 both fail it; older PRs show green only because their runs predate the drift). The whole of the difference is the controller's shard-migration work, which is already deployed on the controller side and simply never regenerated here: Permission.MIGRATE_SHARD, ShardStatus.CUTTING_OVER, the cloud field on ShardUpdateDb, and the new shard_migration_model module. Generated by `just get-types` against controller main 0ec6c6a. Purely additive, nothing is removed, and no shard_core module imports shard_migration_model — this only satisfies the gate. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Regenerates
shard_core/data_model/backendfrom freeshard-controllermain(0ec6c6a).Why now
The
drift-checkjob compares this directory against controllermainbyte for byte, andit is currently red on every PR opened against
main— #173 and #240 both fail it.#180 and #181 show green only because their runs predate the drift. So this is not one
branch's problem; it blocks anything opened today.
What changed
Entirely the controller's shard-migration work, which is already deployed on the
controller side and simply was never regenerated here:
Permission.MIGRATE_SHARDpermission_model.pyShardStatus.CUTTING_OVERshard_model.pycloudonShardUpdateDbshard_model.pyShardMigration*models, statuses and exceptionsshard_migration_model.py(new)Verification
just get-types, not hand-edited.ruff checkclean; the new module imports cleanly and both new enum members resolve.shard_coreimportsshard_migration_model, and no code matchesPermissionorShardStatusexhaustively, so the added members change no behaviour.The only consumer of
ShardStatusoutside the vendored dir istests/conftest.py,which pins
ASSIGNED.Full suite not run locally for this one — it is generated vendored types with no importers;
CI covers it.
🤖 Generated with Claude Code