Repository navigation
Avoid multipart uploads for release artifacts - #1438
Merged
Merged
Conversation
jjhelmus
approved these changes
Nov 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
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.
The ty 0.0.102 release mirror failed when R2 rejected
CompleteMultipartUploadwithInvalidPartfor a 17 MiB archive in the initial mirror job. python-build-standalone uses boto3's 8 MiB default, so 990 of the 991 assets in the current release use the same multipart path. Skipping keys that exist before the transfers start does not resolve an upload whose object was stored but whose response was lost.Raise
multipart_thresholdto 200 MiB so all current release artifacts, the largest of which is about 126 MiB, use a single upload. This deliberately exceeds R2's recommendation to use multipart uploads above roughly 100 MB. Each file loses multipart parallelism and resumability, so a failed upload must restart from the beginning; the release process still uploads four objects concurrently. Single uploads support objects up to about 5 GiB. Artifacts at or above the threshold will use multipart uploads and require additional retry handling.