-
Notifications
You must be signed in to change notification settings - Fork 152
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
resque-pool 0.5.0 broke resque:work rake task #124
Comments
Not intentional. It was meant to fix a problem with running A fix would be as simple as checking to see if either of the two pids have been set, and if neither have then default to normal behavior. |
Hey guys,
I'm not sure if that was intentional, but resque-pool 0.5.0 (specifically, this commit: 2f91e91) changed the way
shutdown?
method works and now there is no way to runrake resque:work
without resque pool - it just exits immediately upon exiting the main processing loop (since there are no parent pids registered by resque-pool).Basically, this means that by simply including resque-pool in a Gemfile of a project one loses ability to use resque without executing the resque-pool command.
The text was updated successfully, but these errors were encountered: