Repository navigation
fix: preserve queued/running status and avoid false failure labels - #12
Merged
Merged
Conversation
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.
October 4 incident follow-up. Preserve the latest job status and execution identity in partial outcomes rather than retaining unknown after a started/job event. Do not print Failed when there is only missing/unconfirmed output. Never resubmit or cancel as a side effect. Three new rendering tests cover interrupted running streams, queued EOF, and terminal authority. All 89 local tests pass (local Node 20; CI must verify supported Node 22). Server worker recovery and credit remediation are separate; this does not claim to fix infrastructure or change polling deadlines.