Skip to content

Settle sibling storage operations before propagating failures - #1

Merged
rawsh merged 1 commit into
release/v0.1.10from
feature/storage-failure-settlement
Oct 4, 2026
Merged

rawsh merged 1 commit into
release/v0.1.10from
feature/storage-failure-settlement

Conversation

@rawsh

@rawsh rawsh commented Oct 4, 2026 •

Copy link
Copy Markdown
Collaborator

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.

Signed-off-by: Robert Washbourne <rawashbourne@gmail.com>
@rawsh
rawsh marked this pull request as ready for review October 4, 2026 08:50
@rawsh
rawsh merged commit b3b4827 into release/v0.1.10 Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant