Closed pluby closed 2 years ago
Sorry for the issue and the late response, this seems to be a misbehavior of the current logic. To fix it temporary, in onError
, simply call next(err)
. I will fix it this week. So sorry again!
This should be fixed in ad857bedb0996312ad3a5ea966ce3a60417429a6. Please reopen if it has not. Thank you.
Thanks.
I had an error handling issue and wrote this test for it but was unable to resolve the problem:
There are two issues revealed by this test:
res.end("bad")
code.