Closed mccare closed 3 years ago
I guess this is by design, since the tests also test for this behaviour.
Yes exactly.
The docs however do not reflect this:
Set a global error handler.
handler(err, task)
will be called when any of the tasks return an error.
Same situation here. I think that the documentation should be updated to reflect this behaviour...
My impression of error handler was, that it would handle the error and not pass it on. The error handler is called also every time (with error == null).
Am I setting up the queue wrong or should I write a worker wrapper for suppressing/handling the error? Thanks for some insight, looking forward to the "broken promise" talk! Head is spinning :-)