| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There are cases where the `'clientError'` event can be emitted multiple times, even if the socket is correctly destroyed. Fixes: nodejs#51073
|
Review requested:
|
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
👍
Nice work, thanks @lpinca! I can imagine other solutions to fix this, like batching client errors, but one way or another they'd end up changing more sensitive existing behaviour elsewhere, so just dropping the incorrect warning seems much simpler.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
Sorry, I don't understand this. If we remove this, we will reopen #43548. Or am I missing anything? |
Sorry, something went wrong.
No, the fix for #43548 is still there. We added the warning because we could not reproduce the issue in a legit way. We can now and the warning is misleading. |
Sorry, something went wrong.
|
Oh, I see. Makes sense now. Thanks! |
Sorry, something went wrong.
Sorry, something went wrong.
|
this is not present in latest node 18, right? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
There are cases where the 'clientError' event can be emitted multiple times, even if the socket is correctly destroyed.
Fixes: #51073