-
Notifications
You must be signed in to change notification settings - Fork 62
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
Allow cleanup of only locks #86
Comments
|
Thanks for the report; it is fixed on git now (and will be part of the next release) |
luispedro
added a commit
that referenced
this issue
May 19, 2022
This was a big bug: the cleanup did not preserve the active tasks at all! closes #86
I just released |
Thanks so much for your incredibly rapid response! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently had an issue with a few of my jug processes being killed and therefore locks being kept on some active tasks. Normally, I would just delete the lock files in the
jugdir
, but I was using the Redis backend, so this was not possible. As suggested in the docs, I ranjug cleanup
, expecting only the locks to be cleared; I was surprised to find the completed jobs cleared as well.Is there any way to have
jug cleanup
only clear the locks? If not, can there be an option for this?The text was updated successfully, but these errors were encountered: