fix(recovery): detect undispatched assigned intents - #203
Merged
Conversation
Contributor
Author
|
Retriggering the same exact head after the GitHub Actions major outage began accepting new workflow events; the original pull_request event produced no check suite. |
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
1 participant
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.
Closes the missing detector behind #198. A central queue intent can be durably assigned while no corresponding GARM instance is ever created; sibling scale sets keep the process heartbeat fresh and no provider retry exists. The portable recovery observation now accepts this exact aged signature and triggers checkpoint-first manager recovery without waiting for unrelated process health to fail.\n\nThe estate adapter will bind it to assigned queue identity plus the authoritative workflow_jobs row lacking instance_id.\n\nVerification: make verify.