Right now, if a user sends repeated KeyboardInterrupt signals it's possible for diskcache to get stuck in a locked state because the cleanup logic that's meant to unlock the cache never gets executed.
When I send a KeyboardInterrupt while a ProcessingPool.map() is being called, a large scramble of stack trace is printed and my terminal hangs indefinitely. I can see all processes are still present ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results