-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call listner.onFailure when lock creation failed #435
Conversation
Signed-off-by: Heemin Kim <[email protected]>
@heemin32 could you rebase your changes? |
Already did. |
Codecov Report
@@ Coverage Diff @@
## main #435 +/- ##
=========================================
Coverage 29.19% 29.19%
Complexity 98 98
=========================================
Files 22 22
Lines 1185 1185
Branches 109 109
=========================================
Hits 346 346
Misses 818 818
Partials 21 21 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @heemin32 for these changes, lgtm. Lets backport this to 2.x as well
Signed-off-by: Heemin Kim <[email protected]> (cherry picked from commit d2e0ac0)
Signed-off-by: Heemin Kim <[email protected]> (cherry picked from commit d2e0ac0) Co-authored-by: Heemin Kim <[email protected]>
Description
When lockId is too long, it silently call
onResponse
of listener withnull
. In such case, we don't know if lock acquire is failed because the lock is being hold by other processor, or lock creation itself is failed. We should callonFailure
withexception
so that caller can handle such case accordingly.Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.