-
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
Rescue from ScriptError #373
Rescue from ScriptError #373
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! I made one suggestion to make the test more explicit
4d4ea86
to
41c2c92
Compare
I think this PR shouldn't be merged. If you have error in your code then you have to fix it in your code. |
Background processing should be reliable. It should not become frozen if coder writes bad code leading to error. |
@kalys thanks for weighing in. Errors have always been rescued in workers and passed to the |
Coder should cover his/her code with tests to detect @gabrieljoelc
It's not ok to catch error when some feature is unavailable in current ruby implementation or OS. http://chrisstump.online/2016/03/23/stop-abusing-notimplementederror/ |
We catch the base class here not
|
@gabrieljoelc Unfortunately, the problem of stale workers is still actual. Some gems introduce their own exceptions not based on |
I found that sneakers worker becomes frozen after raised NotImplementedError.
Code to reproduce:
This PR fixes it.