-
Notifications
You must be signed in to change notification settings - Fork 74
CP Subsystem - CountDownLatch #225
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
Conversation
|
verify |
8217049 to
ef87776
Compare
Adds the implementation, documentation, code samples and test of CP CountDownLatch. Also, invocation service is editted to return `OperationTimeoutError` instead of `HazelcastTimeoutError` in case of invocation timeouts as the Java client does.
ef87776 to
a0b4e77
Compare
puzpuzpuz
left a comment
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.
LGTM
| self.assertTrue(latch.try_set_count(3)) | ||
| self.assertEqual(3, latch.get_count()) | ||
|
|
||
| def test_try_set_count_when_count_is_already_set(self): |
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.
nit: does it make sense include a test that verifies that try_set_count succeeds once the count goes to zero?
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.
Good idea. I added the extra test case.
goes back to zero.
|
Thanks for the review Andrey, I am merging this PR |
Adds the implementation, documentation, code samples, and test of
CP CountDownLatch.
Also, the invocation service is edited to return
OperationTimeoutErrorinstead of
HazelcastTimeoutErrorin case of invocation timeoutsas the Java client does.
depends on #224