-
Notifications
You must be signed in to change notification settings - Fork 64
Can't CTRL-C
after using go-prompt to select role
#91
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
Comments
problem only happens in exec/console (not something like list) because it is caused by go-prompt Not fixes:
|
Trying a few trick to see if I can get CTRL-C to work after using go-prompt and before the program exits. Whatever go-prompt is doing to the terminal doesn't seem to be resetting correctly? Refs: #91
Marking as blocked at this time since this seems to be a go-prompt bug and I haven't found a work around. Also doesn't seem like go-prompt is being actively maintained :( |
CTRL-C
after using go-prompt to select role
looks like everyone is forking go-prompt and applying this patch: c-bata/go-prompt#239 Note that this patch doesn't fix the CTRL-C bug. |
This seems fixed for me on macOS Ventura 13.4.1, iTerm 3.4.20 and aws-sso v1.12.0 |
Not really fixed, but documented the CTRL-d / exit for users. |
Basically go-prompt is blocking CTRL-C even after you have made a selection and Prompt.Run() has returned. The result is that if you try CTRL-C during AWS SSO / OIDC login/authentication, rather than the tool exiting like the user expects, they just see
^C
printed in the terminal. The only way out is to either:The text was updated successfully, but these errors were encountered: