-
Notifications
You must be signed in to change notification settings - Fork 0
fix(orchestrator): bound each relayfile call so a hung read cannot wedge reconcile (#351) #354
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
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
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.
With the real cloud mount, the transport deadline intentionally expires before the 1.25× orchestrator backstop, but this branch rethrows the transport's
RelayfileOperationTimeoutError, whosephaseis undefined. Consequently the persistedlastErroris onlyrelayfile listTree did not respond within 300000ms, not the documented message containing(GitHub issue ingestion), and operators cannot distinguish the many list/read contexts. Enrich an existing transport timeout withdetails.phasewhen it crosses the orchestrator boundary.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.
Correct — and it defeated the stated purpose of the change, since naming which call was waiting is most of what #351 asked for. My own PR body and the diagnostics doc both quote a message with
(GitHub issue ingestion)that the transport path would never have produced.Fixed in c50ff96:
#withRelayfileOperationnow throwsrelayfileTimeoutWithPhase(error, details.phase), which rebuilds a phase-lessRelayfileOperationTimeoutErrorwith the phase the orchestrator knows and keeps the original ascause. Covered bynames the phase on a timeout the transport raised, not just its own: a mount that throws the exact phase-less error the real transport raises, with the orchestrator's own budget deliberately out of reach so the backstop cannot be what produces the message. Ablation confirms it fails on the phase assertion specifically.