-
Notifications
You must be signed in to change notification settings - Fork 331
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
rake sneakers:run sometimes ignores SIGINT #41
Comments
Hi Abe, what you're describing has to do with how Ruby 1.9 and 2.0 handle signals (it somehow changed). I have contributed a fix to To get some more insights I would love to have a look at the Gemfile.lock you were using at the time of this issue. If you could please gist it, I'd be happy to try and help. |
Sure, here you go: https://gist.github.com/abevoelker/3550ea9005317d63ad27 (Gist stupidly tries to syntax highlight it as JSON, even when I try to override it w/ Text) |
Just a guess, maybe you have
somewhere? It will catch ctrl-c and SIGTERM |
Sometimes when running the rake task, the workers do not respond to SIGINT. I send a Ctrl+c and it says it's shutting down workers, but it doesn't. In fact I can hold Ctrl+c and it just floods the screen with "Shutting down workers" messages, but doesn't shut everything down. If I send the rake task to background with Ctrl+z and try to
kill
the PID, it likewise doesn't respond. I end up having tokill -9
it.In my initializer I have
:daemonize => false
, in case that's relevant.Here is the console output from a run I just had where this occurred (sorry for the weird linebreaks, copied+pasted from my console):
The text was updated successfully, but these errors were encountered: