-
Notifications
You must be signed in to change notification settings - Fork 30k
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
http: don't destroy completed request #33120
Conversation
1bab1cb
to
0111fee
Compare
0111fee
to
302cb98
Compare
@nodejs/http @nodejs/web-server-frameworks @szmarczak |
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.
lgtm.
What's the semver level?
I would argue patch. It's kind of a bug fix. |
@nodejs/http |
Calling destroy() on a completed ClientRequest, i.e. once 'close' will be emitted should be a noop. Also before emitting 'close' destroyed === true. Fixes: nodejs#32851
f0028b4
to
8ff38ec
Compare
@nodejs/http, this needs another review |
Landed in b04e884 |
That's the fastest I've probably ever seen something I review get landed without it being fast-tracked :] |
@benjamingr I was so happy that you reviewed this PR that I just had to land it as quickly as possible to celebrate! 🍾 |
Calling destroy() on a completed ClientRequest, i.e.
once 'close' will be emitted should be a noop. Also
before emitting 'close' destroyed === true.
Fixes: #32851
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes