contentutil: thread context through registry refs - #6985
Open
crazy-max wants to merge 1 commit into
Open
Conversation
crazy-max
force-pushed
the
fix-provider-from-ref-context
branch
from
July 25, 2026 09:15
c95db72 to
adc220e
Compare
crazy-max
marked this pull request as ready for review
July 27, 2026 21:28
crazy-max
force-pushed
the
fix-provider-from-ref-context
branch
2 times, most recently
from
August 24, 2026 14:14
9712386 to
7ec5688
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
fix-provider-from-ref-context
branch
from
August 24, 2026 14:31
7ec5688 to
5a052dc
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.
relates to moby/moby#48830
This makes the contentutil registry helpers respect caller cancellation when resolving, fetching, and pushing registry refs. The previous implementation used
context.TODO()inside the helper, which meant a hung or unresponsive registry request could outlive the test sandbox context and wait for the outer test timeout instead.