Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No job should be run if a signal was caught #10

Open
twidi opened this issue Oct 4, 2013 · 1 comment
Open

No job should be run if a signal was caught #10

twidi opened this issue Oct 4, 2013 · 1 comment
Assignees
@twidi
Labels
bug wontfix

Comments

@twidi
Copy link
Collaborator

twidi commented Oct 4, 2013

If a signal was caught when the worker is waiing for a response from redis (during the blpop call), the worker stil waits for redis and then run the returned job.

It should not happen.
@ghost ghost assigned twidi Oct 4, 2013
@twidi
Copy link
Collaborator Author

twidi commented Nov 9, 2013

Know that you release the signal cacht, the new ctrl-c is hit by the redis connection which is then cut (but not raise the correct error on our side, though)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@twidi twidi

Labels
bug wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@twidi