-
Notifications
You must be signed in to change notification settings - Fork 24
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
Do not continue doing things after Ctrl+C #56
base: main
Are you sure you want to change the base?
Conversation
e31b682
to
3967fa9
Compare
@@ -322,7 +322,7 @@ def scary_cleanse_warning(*args) | |||
sleep 60 | |||
rescue Interrupt | |||
log "" | |||
exit 0 | |||
Kernel.exit 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
THese seemed a safe exit code change to make, because this is handling for when the operator explicitly does not pass the --yes
argument that will bypass the wait period
Interrupted CLIs typically exit non-zero.
3967fa9
to
80cfc6a
Compare
@marcparadise Is this something we want to get merged in still? Seems worth shipping. |
Yeah, this looks like something that we still want. |
Call Kernel.exit! 1 to force an immediate error-exit if the operator uses Ctrl+C to prevent performing post-hook steps. Signed-off-by: Marc A. Paradise <[email protected]>
80cfc6a
to
2c7b3b7
Compare
Kudos, SonarCloud Quality Gate passed!
|
Call Kernel.exit! 1 to force an immediate error-exit
if the operator uses Ctrl+C to prevent performing post-hook steps.
Signed-off-by: Marc A. Paradise [email protected]