Repository navigation
feat: add bounded mixed upload and download queue - #19
Merged
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
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.
Mixed uploads and downloads can now share a caller-owned queue with bounded chunk scheduling, per-connection admission, pause/resume, rate limits and observable verified completion. Small eligible transfers can progress while large transfers yield, another connection is saturated, or a retry backs off.
The queue reuses the existing upload and artifact verifiers. Only identical chunk operations retry SDK-classified 429/503, network failures and request timeouts within attempt/deadline budgets. Begin, commit and sink operations are never automatically replayed. Progress separates acknowledged, attempted, retried and resumed bytes; 100% remains unverified until a final receipt passes. Upload session limits, partial retention, cancellation and live-instance pause semantics are explicit.