Skip to content
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

PotteryRedLock.locked() does not show real ttl #701

Open
matroskin8 opened this issue Aug 21, 2023 · 1 comment
Open

PotteryRedLock.locked() does not show real ttl #701

matroskin8 opened this issue Aug 21, 2023 · 1 comment
Assignees
Labels

Comments

@matroskin8
Copy link

Describe the bug
If we define two objects of PotteryRedLock with same key (for example at different app instances), their locked() methods does not show states of other object

To Reproduce
Steps to reproduce the behavior:

PotteryRedLock(key='key', masters=masters, auto_release_time=60).acquire()
PotteryRedLock(key='key', masters=masters).locked()

locked() will return 0, that means lock could be acquired, but second try to acquire will blocks for up to 60 seconds

Expected behavior
locked() returns value close to auto_release_time of first lock

Environment (please complete the following information):

  • OS: [e.g. macOS, Linux]

    uname -a
    Darwin xxx 20.6.0 Darwin Kernel Version 20.6.0: Wed Nov 10 22:23:05 PST 2021; root:xnu-7195.141.14~1/RELEASE_ARM64_T8101 arm64

  • Python version 3.9.15

  • Redis version 6.2.5

@brainix brainix self-assigned this Aug 21, 2023
@brainix brainix added the bug label Aug 21, 2023
@matroskin8
Copy link
Author

Found that locked() returns wrong value coz self._uuid = None, should it check db if no uuid?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants