-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
[v14.x Backport] http: don't cork noop .end() #36940
[v14.x Backport] http: don't cork noop .end() #36940
Conversation
PR-URL: nodejs#36633 Fixes: nodejs#36620 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> (cherry picked from commit ec794f9)
I can't directly request a review on the PR, so according to the original PR reviewers, @mcollina @benjamingr @danielleadams @rickyes could you please take a look? Thanks! |
This needs a CITGM run before landing. |
Ok thanks! Do I need to do anything else, or will the required labels be automatically added for CI testing? |
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2570/ might do the trick |
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.
v14.x-staging CITGM because there are a few suspects: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2572/ |
@mcollina sorry but didn't get what "too quick" was referring to... 😄 |
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
I needed to check the result of CITGM on v14.x-staging
Do I need anything else to prep the PR or we are good to go now? |
This comment has been minimized.
This comment has been minimized.
Landed in 15a16cd...5593187 (v14.x-staging) |
Backport to v14 of #36633
It has been merged to latest v15 but for the time being not in the v14.x branch.
Some changes needed because code in
_http_outgoing.js
and tests is different between versions v14 and v15