fix: lock_if_exist + aggressive locking #705
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
…alculated as successfully locked for aggressive locking Signed-off-by: ekexium <ekexium@gmail.com>
ekexium
force-pushed
the
fix-aggresssive-locking-with-lock-if-exist
branch
from
c6ad906 to
b520845
Compare
|
@cfzjywxk @sticnarf PTAL |
cfzjywxk
reviewed
Feb 17, 2023
sticnarf
approved these changes
Feb 17, 2023
cfzjywxk
approved these changes
Feb 17, 2023
ekexium
force-pushed
the
fix-aggresssive-locking-with-lock-if-exist
branch
from
e3bcfae to
3ac677a
Compare
|
/merge |
ekexium
force-pushed
the
fix-aggresssive-locking-with-lock-if-exist
branch
from
3ac677a to
0b14b98
Compare
12 tasks
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.
Locking commands skipped by
lock_only_if_existswere mistakenly calculated as successfully locked for aggressive locking.