-
Notifications
You must be signed in to change notification settings - Fork 85
SIGINT cannot be caught #191
Comments
thanks for the report. this may be a consequence of adding the ability to kill infinite loops with |
@metametadata can you repro this on a Lumo version < 1.4, e.g. 1.2 or 1.3? |
Yes, looks like a regression as it works in 1.3.0 as expected:
|
Turns out this is actually fixed in master. Please reopen if still an issue. |
Thank you, looking forward to the next release! |
In v0.6.0 the issue is still reproducible, but only when some ns is required in the script. E.g.:
|
It looks like this issue is happening no matter what. I see the same behavior whether at the REPL or in a script. When ctrl-c is pressed, lumo exits without ever calling the SIGINT handler.
|
fwiw I'm still seeing this issue on 1.9.0-alpha. |
Here's a repo for reproducing the steps in
Lumo
andNodeJS
. I've checked the behaviour onSIGINT
,SIGTERM
,SIGQUIT
andSIGHUP
and noticed the problem only withSIGINT
.Steps:
Run Lumo app which listens to
SIGINT
signal:lumo app.cljs
Send
SIGINT
(e.g. by clickingCtrl+C
or by executingkill -INT $!
).Actual: app exits without first catching signal event.
Expected: app is able to intercept a signal (because
NodeJS
apps are able to catch this signal).This feature is important for apps needing to do some cleanup before exiting. E.g. I use signal-exit module to do cleanup.
The text was updated successfully, but these errors were encountered: