| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Do not swallow error details when reporting UV_EPROTO asynchronously, and when creating artificial errors. Fix: nodejs#3692
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
There was a problem hiding this comment.
I'd add a CHECK_EQ(error_, nullptr), otherwise it's a memory leak waiting to happen.
EDIT: Or call ClearError() first.
Sorry, something went wrong.
There was a problem hiding this comment.
Ack.
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Landed in ff4006c, thank you everyone! |
Sorry, something went wrong.
Do not swallow error details when reporting UV_EPROTO asynchronously, and when creating artificial errors. Fix: nodejs#3692 PR-URL: nodejs#4885 Reviewed-By: Shigeki Ohtsu <ohtsu@iij.ad.jp> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
| Back | FazBrowse Home | New Git URL |
Do not swallow error details when reporting UV_EPROTO asynchronously,
and when creating artificial errors.
Fix: #3692
R = @bnoordhuis or @shigeki
cc @nodejs/crypto