-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fixing redis locking for 5000 seconds unintentionally #5
Conversation
@karljin I think this PR is still valid right? |
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.
I don't recall anymore. Would recommend a fresh look. I would keep the number of unknowns minimum for py3 migrations.
@@ -15,13 +15,13 @@ | |||
|
|||
|
|||
@contextlib.contextmanager | |||
def simple_lock(lock_key, timeout=5000): |
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.
is 5 sec enough ? should we make it longer.
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.
it's always been meant to be 5 seconds. the fact that it's locking for 5000 seconds is purely accidental and "bad"
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.
assuming this can be tested properly
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
Same problem as what we see in transmissions