Repository navigation
Conversation
A multi-node export failed as soon as the node chosen for an image could not export it, even when another node held a complete copy. A failed share now moves to the other nodes that hold its images, reading any node the first plan skipped. An image no node can supply still fails with the original diagnostics and keeps the existing archive. Part of #8251 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A content repair can re-pull a tag@digest image by its tag, so a node archive can name the tag instead of the planned reference. Pin that a multi-node export still publishes it instead of refusing a complete archive. Part of #8251 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
✅
|
devantler
added a commit
that referenced
this pull request
Nov 11, 2026
devantler
added a commit
that referenced
this pull request
Nov 11, 2026
devantler
added a commit
that referenced
this pull request
Nov 11, 2026
Contributor
Author
The head remains With no live worktree holder and no newer branch activity, I restarted Go validation and KSail CI. The Go run is on attempt 2; KSail CI accepted the rerun and is queued. Keep this draft until the required checks settle, then obtain a current-head review and verify the image-export behavior before promotion. These rerun receipts do not establish readiness. |
Contributor
Author
User trial at
🤖 Generated with Claude Code |
Contributor
Code coverage overviewLanguages: Go Go / code-coverage/go
View coverage of the 7 most impacted files.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Keep the export plan alongside main's platform notice after an export. Part of #8251 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Why
Exporting images from a cluster with several nodes gave up as soon as the node picked for an image could not export it, for example because its copy was damaged, even when another node held a complete copy.
What
When a node cannot export its share, the export now takes those images from another node that holds them, and only fails, keeping the previous archive, when no node can supply an image. A new test also pins that an image a repair re-pulled under its tag is still published. The nested multi-node system test that this issue also carries stays open there.
Part of #8251
🤖 Generated with Claude Code