Repository navigation
fix: prevent stale cluster transitions from overriding newer requests - #79
Merged
dmux merged 2 commits intoOct 27, 2026
Merged
Conversation
Collaborator
Author
|
All checks have passed. This PR is ready to merge. |
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.
Cluster lifecycle requests schedule delayed state transitions. A later request now replaces the earlier transition, so a pending start cannot move a terminated cluster back to RUNNING. Permanent deletion and state reset also invalidate pending transitions.
Adds an HTTP regression for creating a cluster and immediately terminating it.
Validation: Ruff format and lint passed; all 10 cluster tests passed, including the regression with short start/terminate delays.
Fixes #46