fix: add limit to nix copy to avoid hitting s3 upload limits#2039
Merged
fix: add limit to nix copy to avoid hitting s3 upload limits#2039
Conversation
soedirgo
approved these changes
Feb 7, 2026
encima
pushed a commit
that referenced
this pull request
Feb 23, 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
3 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.
in PR ci runs like https://github.com/supabase/postgres/actions/runs/21781372775/job/62845918939?pr=2028 we hit s3 upload limits since no max-jobs was set, nix copy has no limit.
We have multiple CI jobs potentially uploading concurrently to the same /nar/ prefix, a conservative per-job limit would be:
This should help with the fact that we have potential to launch 5-10 CI runs at once.