stop splitting the TUF repo on the 1 GiB boundary #5325
Merged
Conversation
This file contains 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
labbott
approved these changes
Apr 3, 2024
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.
Follow-up to #5316, split to prevent breaking various scripts until v7 is out the door.
Per chat and #5316 (comment), Buildomat has supported >1 GiB uploads for a while, but we've seen issues with downloading files that large. There's now range request support, so retrying failed downloads is no longer catastrophic.
However a lot of scripts are out there that assume we must download a parta/partb. I don't want to prevent people from deploying quickly on dogfood while we're in the run up to a release, unless whoever's on dogfood updates wants to merge this and fix the script.