-
Notifications
You must be signed in to change notification settings - Fork 43
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
Handle KeyboardInterrupt #970
Labels
Comments
Closed
dacevedo12
added a commit
to dacevedo12/makes
that referenced
this issue
Feb 9, 2024
- both in subprocess and main - to catch the case where the tui hasn't even started yet
dacevedo12
added a commit
to dacevedo12/makes
that referenced
this issue
Feb 9, 2024
- both in subprocess and main - to catch the case where the tui hasn't even started yet Signed-off-by: David Acevedo <dacevedoa12@gmail.com>
dacevedo12
added a commit
to dacevedo12/makes
that referenced
this issue
Feb 9, 2024
- both in subprocess and main - to catch the case where the tui hasn't even started yet Signed-off-by: David Acevedo <dacevedoa12@gmail.com>
dacevedo12
added a commit
to dacevedo12/makes
that referenced
this issue
Feb 9, 2024
- both in subprocess and main - to catch the case where the tui hasn't even started yet Signed-off-by: David Acevedo <dacevedoa12@gmail.com>
dsalaza4
added a commit
that referenced
this issue
Feb 9, 2024
feat(build): #970 handle keyboard interrupt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When canceling the execution of a job via ^C a traceback is shown
It leaves one wondering if there's a bug or if the underlying process actually stopped
The text was updated successfully, but these errors were encountered: