solver: lock before using actives#3938
Merged
tonistiigi merged 1 commit intomoby:masterfrom Jun 8, 2023
Merged
Conversation
tonistiigi
reviewed
Jun 8, 2023
Member
tonistiigi
left a comment
There was a problem hiding this comment.
I wonder if we should just do one lock in WalkProvenance? Doing the lock/unlock separately for each vertex may have a bigger overhead.
906e3a5 to
4ddb9e8
Compare
Job.walkProvenance needs to acquire a read lock before accessing j.list.actives. The actual lock is acquired/released under WalkProvenance to prevent multiple locks/unlocks while walkProvenance recurses. Signed-off-by: Alex Couture-Beil <alex@earthly.dev>
4ddb9e8 to
09325e7
Compare
tonistiigi
approved these changes
Jun 8, 2023
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.
This fixes: