Repository navigation
Add artifact limits and shared rate-limit transport - #102
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Add
fetch.WithMaxArtifactSizefor declared and streamed response bodies, including observed downloads. Reject oversized declarations before reading, accept exact-limit bodies, and keep observations incomplete on overflow. Local size rejections do not trip circuit breakers.Add an optional
client.RateLimitGatethat can be shared by metadata and artifact HTTP clients. Expose typed held errors, hold snapshots, prechecks, and callbacks for logging and metrics. Share overflow-safe Retry-After parsing with the metadata client, support HTTP dates, and cap repeated fallback holds without overflowing. Metadata retries stop on held errors and on 429 responses with a usable Retry-After. No new dependencies.