-
Notifications
You must be signed in to change notification settings - Fork 277
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
Incorrectly handles SIGINT #1956
Comments
I'm seeing the same issue here, being able to use CTRL-C to actually stop pkg would be good. |
Packaged ports from latest, following a major upgrade of base (without pkgbase) from 13.2-RELEASE-p7 to 14.0-RELEASE-p2. In this case, I keyed Control-C (00:01:32 on the timeline of a screen recording) after it became clear that n would not have the required effect: 00:37:18 on the timeline, with an assumption that things would be endless following the attempted cancellation, I restarted the OS: Please note, I don't need help with this particular package upgrade scenario; it was a test. No frustration for me. The three frames from the recording are, partly, to demonstrate the potential for a user to be frustrated in an OS upgrade situation. |
Fixed? From ports-mgmt/pkg: update to 1.21.0 · freebsd/freebsd-ports@c923e0d (2024-04-02):
|
I just reported this as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280092 It's still an issue in 1.21.3. (Note that a similar behavior happens on EOF = ^D, for different internal reasons maybe.) |
So I run
pkg upgrade
(pkg 1.16.3), it shows what's it going to do and asksProceed with this action? [Y/n]:
I hit ^C to interrupt it, but instead it proceeds:
By
/tmp
after the prompt I suspect that multiple processes are involved here, one of which is terminated, but another erroneously continues.The text was updated successfully, but these errors were encountered: