Join GitHub today
NullLock.acquire takes exactly 1 argument (2 given) #97
Migrated issue, originally created by Jamie Lennox (jamielennox)
So this is a transient bug in a keystone deployment i'm working on that i haven't figured out the source of yet, however the fix i think is reasonably clear.
The Null cache backed's NullLock.acquire does not accept any arguments  however it's called with wait=True  and so gives a ValueError. I'm not sure how this went unnoticed for so long or why I'm only seeing it on some runs, but the acquire function should definitely be accepting the wait parameter like other lock implementations.
Michael Bayer (zzzeek) wrote:
NullLock.acquire should accept wait parameter, return boolean
The interface for acquiring locks specifies that they should accept and