-
Notifications
You must be signed in to change notification settings - Fork 0
fix(reconciler): finalize progress on interrupt, classify interrupts distinctly, surface flight-cancel rejections #204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| "@agent-bundle/runtime": patch | ||
| --- | ||
|
|
||
| Finalize progress reporters on setup and stream interruption with an abort | ||
| outcome, and surface Flight reader cancellation failures that do not mask an | ||
| earlier stream failure. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the decoded root has no pending boundaries but the Flight source remains open, this unconditional
Deferred.await(flightDone)prevents bothstream()anddispatch()from ever emittingcomplete. Unlike the pending-boundary path, it does not race againstsequence.remainingMs, so even a configuredmaxElapsedMscannot terminate a stuck or long-lived transport; race this wait with the render deadline and tear down the Flight source on timeout.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in #214 (merged as 4daf388). The no-pending-boundaries EOF wait is now raced against the render deadline through the same
waitOrDeadlinehelper the pending-boundary path uses, so a configuredmaxElapsedMsterminates a stalled Flight transport withelapsed-time-exceededand the source reader is cancelled on teardown. Regression test drives bothstream()anddispatch()against a never-closing Flight source withmaxElapsedMs: 150and asserts timely failure plus exactly one source cancel.