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.

Sign up for GitHub

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

Jump to bottom

Improve error handling/diagnostics #26

Open

bedge opened this issue Apr 1, 2024 · 0 comments

bedge commented Apr 1, 2024

Just had a case where manually aborting a job did not release the mutex.
Have not tracked down the specifics yet, but, regardless it happened.

Things I noticed were:

Not clear how to tell what job is the owner of the mutex
What's the appropriate action to take to release the lock? (Other than simply deleting the branch)

This does make me want:

Max wait timeout. In case an aborted job fails to release the mutex again, this would let the next in line caller force the issue and take ownership.
A notification channel for cases where the above happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment