feat: add in-memory lock #399
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
Codecov Report
@@ Coverage Diff @@
## main #399 +/- ##
==========================================
+ Coverage 59.83% 60.18% +0.35%
==========================================
Files 116 117 +1
Lines 6197 6252 +55
==========================================
+ Hits 3708 3763 +55
Misses 2128 2128
Partials 361 361
Continue to review full report at Codecov.
|
seeflood
requested changes
Mar 1, 2022
seeflood
requested changes
Mar 1, 2022
seeflood
requested changes
Mar 1, 2022
…add_in_memory_lock # Conflicts: # components/lock/in-memory/in_memory_lock.go
zhenjunMa
previously approved these changes
Mar 11, 2022
zhenjunMa
approved these changes
Mar 11, 2022
|
This component can make debug easier.Thanks! |
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.
What this PR does:
add lock in memory
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?: