http: fix release race between cache and snapshot #6292
Merged
Conversation
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
Signed-off-by: Tonis Tiigi <[email protected]>
tonistiigi
force-pushed
the
http-release-fix
branch
from
259108e to
e7a66cb
Compare
Signed-off-by: Tonis Tiigi <[email protected]>
tonistiigi
force-pushed
the
http-release-fix
branch
from
e7a66cb to
80766cd
Compare
Fixes issue where HTTP result can be released after metadata resolve and rest of the build might pull new (potentially different) data in again. Signed-off-by: Tonis Tiigi <[email protected]>
Member
Author
|
Pushed additional fix for a similar case in relation to race between metadata resolve and cache/snapshot of the same URL. |
crazy-max
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix issue where reference pulled for HTTP URL cache key digest computation can be released before the
Snapshotmethod of the same step runs. This can cause duplicate pulls, or if data has changed upstream it would return "digest mismatch" error.