Repository navigation
Settle sibling storage operations before propagating failures - #1
Merged
Merged
Conversation
Signed-off-by: Robert Washbourne <rawashbourne@gmail.com>
rawsh
marked this pull request as ready for review
October 4, 2026 08:50
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.
Settle all sibling PUT and CLEAR operations before propagating the first storage failure.
This prevents late sibling work from escaping the failed batch and preserves the original error.
Proof: combined release tree 93935885 (PRs 3/4 + exact PR1 + corrected PR2) passes 15 source-service and 15 installed-wheel controls, all 3 hooks, and the complete installed suite: 606 passed, 11 existing optional-backend skips, zero failures/errors (job 142562, 0:0). All 113 source blobs and 45 wheel files match. Native source proof only; image and joint trainer-restore qualification remain.