Open
Conversation
Taking the lock is one (atomic) filesystem operation. This prevents race conditions when another process creates the lock after os.Stat() and before os.Create(). Now, If we get the lock, we have the lock. There is a condition where we may miss the lock, but it is released before we open for information purposes. This still counts as missing the lock.
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
1 participant
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.
Taking the lock is one (atomic) filesystem operation. This prevents race conditions when another process creates the lock after os.Stat() and before os.Create(). Now, If we get the lock, we have the lock.
There is a condition where we may miss the lock, but it is released before we open for information purposes. This still counts as missing the lock.