Refactor and export range retry transport#2012
Merged
markusthoemmes merged 1 commit intochainguard-dev:mainfrom Jan 14, 2026
Merged
Refactor and export range retry transport#2012markusthoemmes merged 1 commit intochainguard-dev:mainfrom
markusthoemmes merged 1 commit intochainguard-dev:mainfrom
Conversation
This transport had some weirdness about it in terms of using an HTTP client internally instead of the "usual" transport layering. This fixes that and also avoids storing a context unnecessarily. That makes the transport itself stateless and statically usable for clients as well. Fixes a couple of other nits around the transport as well.
jdolitsky
approved these changes
Jan 13, 2026
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
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.
This transport had some weirdness about it in terms of using an HTTP client internally instead of the "usual" transport layering. This fixes that and also avoids storing a context unnecessarily. That makes the transport itself stateless and statically usable for clients as well.
Fixes a couple of other nits around the transport as well.