You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now aioredlock doesn't track locks on redis, as soon as the lock becomes valid it will be valid forever even when it will expire on server side.
For short living locks it is not a problem, for long living locks application should periodically extend all own lock lifetimes.
Periodically lock checking/extension could be implemented in aioredlock, but someone have to do it.
"Expire the lock valid attribute according to the lock validity in a safe way if possible."
I don't understand what this means? Does it mean that a lock is valid even if it's released or got into timeout?
The text was updated successfully, but these errors were encountered: