feat: lock when indexing #1030
Open
feat: lock when indexing #1030
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
wolfv
force-pushed
the
lock-when-indexing
branch
from
5825912 to
84f402f
Compare
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.
I shamefully copied the code from
rattler_repodata_gatewayto add aLockedFileto the indexing.We would like to prevent multiple instances of e.g.
rattler-buildto write to therepodata.jsonat the same time.A companion PR is in rattler-build about compressing the packages into a temporary file, and then atomically renaming them once they are finished.
Both are made in order to improve the experience when running multiple builds in parallel.