fix: abort sync when child manifest blobs are missing#26
Merged
davidpoblador merged 1 commit intomainfrom Apr 2, 2026
Merged
Conversation
Previously, the sync worker would silently skip missing blobs and push child manifests upstream without them, resulting in broken images. Now it validates all blobs exist locally before pushing anything, and raises SyncMissingBlobsError so the sync retries with backoff. Also fixes the blob count log to include child manifest blobs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
SyncMissingBlobsErrorwhen blobs are missing, triggering retry with exponential backoffTest plan
test_sync_one_fails_when_child_manifest_blobs_missingverifies sync raises error and marker stays pending🤖 Generated with Claude Code