refact(pull): verify local blob integrity before pulling#129
Open
refact(pull): verify local blob integrity before pulling#129
Conversation
Verify hashes of app blobs already present in the local store before running an update/pull operation. This ensures we detect and re-download blobs that have become corrupted due to external factors (e.g., disk degradation). Checking only the blob size is not sufficient, as corrupted blobs may still match the expected size while having invalid content. Signed-off-by: Mike Sul <mike.sul@foundries.io>
mike-sul
force-pushed
the
refact/check-blob-hashes-on-pull-v97
branch
from
a770731 to
819a36c
Compare
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.
Verify hashes of app blobs already present in the local store before running an update/pull operation. This ensures we detect and re-download blobs that have become corrupted due to external factors (e.g., disk degradation).
Checking only the blob size is not sufficient, as corrupted blobs may still match the expected size while having invalid content.