Repository navigation
Conversation
check, pull and update init load an app's metadata from the registry even when every metadata blob is already in the store, so they cost registry round trips and fail offline for a fully fetched app. Load the tree through a provider that serves a blob from the store once a first read has verified its size and digest, and falls back to the registry if it is missing or invalid there, so pull still repairs a corrupt blob. It reports the remote type so the loaded tree keeps the same nodes as one loaded from the registry. Fixes: #101 Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Mike Sul <mike.sul@foundries.io>
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.
check, pull and update init load an app's metadata from the registry even when every metadata blob is already in the store, so they cost registry round trips and fail offline for a fully fetched app.
Load the tree through a provider that serves a blob from the store once a first read has verified its size and digest, and falls back to the registry if it is missing or invalid there, so pull still repairs a corrupt blob. It reports the remote type so the loaded tree keeps the same nodes as one loaded from the registry.