search

ngless-toolkit / ngless

NGLess: NGS with less work
https://ngless.embl.de
Other
142 stars 24 forks source link

Explicit way of invalidating locks #15

Open unode opened 7 years ago

unode commented 7 years ago

Sometimes when I'm testing things, jobs fail and leave active locks behind. Subsequent calls fail as they cannot obtain any lock.

Currently I workaround this by removing the ngless-locks folder or the matching subfolder inside ngless-locks which is suboptimal.

With that said, it would be nice if after:

ngless --options ... mycustomscript.ngl

one could:

ngless --clear-locks mycustomscript.ngl
luispedro commented 7 years ago

+1 but this is hard to implement with the current structure.

At the moment, the locks will eventually expire, but I agree it can be annoying to wait for this.