Skip to content

Fix semaphore usage#321

Merged
bbangert merged 2 commits intopython-zk:masterfrom
harlowja:fixed-sempahore
May 28, 2015
Merged

Fix semaphore usage#321
bbangert merged 2 commits intopython-zk:masterfrom
harlowja:fixed-sempahore

Conversation

@harlowja
Copy link
Copy Markdown
Contributor

The semaphore should be passing the blocking argument to the
underlying lock that is used (so it is non-blocking as well) and
it should also be passing the timeout as well.

The non-blocking result should also not add a watch that will
later attempt to get the least (another call to acquire should be
used instead, or the blocking mode should be used instead).

Joshua Harlow added 2 commits May 27, 2015 16:23
The semaphore should be passing the blocking argument to the
underlying lock that is used (so it is non-blocking as well) and
it should also be passing the timeout as well.

The non-blocking result should also not add a watch that will
later attempt to get the least (another call to acquire should be
used instead, or the blocking mode should be used instead).
After the initial lock is acquired the timeout can now
be different (due to time used getting the lock) so add
a little helper class to ensure that the timeout is
changed due to the elapsed time.
bbangert added a commit that referenced this pull request May 28, 2015
@bbangert bbangert merged commit e228ed2 into python-zk:master May 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants