-
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
[v10.x] Revert "http: always emit close on req and res" #21809
Conversation
I would prefer if this is a @nodejs/tsc decision. Should we put it in the agenda for next week? |
Sure. Added the label. |
Node.js 10 has had the change for almost twice as long as it didn’t have it, and we’ve done security releases since then (i.e. we expect people to use versions that have it)… not knowing much about the subject matter, I’m not sure reverting is ideal?i |
From different point of view - since 10.2.0 it was an undocumented API change, it became part of the documentation in version 10.6.0 just 10 days ago... How about projects relying on the previous documented version added in 0.6.7 released in January 2012? I think the number of them will be slighly bigger;) |
Note from TSC meeting: we also need to revert the documentation change. |
From the discussion in the TSC meeting I'm +1 to reverting. |
This is the documentation change #21047. |
Was there a resolution in the TSC meeting? Should the |
@Trott we did not have quorum. The proposed path is to revert this in Node 10, but leave it in in master. This approach would need necessarily 2 TSC signoffs because it's a retroactive semver-major change that should not have landed in master without 2 TSC signoffs. |
Doc change reverted |
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
CI: https://ci.nodejs.org/job/node-test-pull-request/15944/ Is this going to break |
@targos I do not think so. What broke eos was 8029a24. cc @mafintosh to confirm before landing. |
|
CI is green. This needs at least one more @nodejs/tsc signoff. |
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.
Rubber stamp LGTM
@nodejs/release @nodejs/lts I think this is ready to land. |
I'm going to add this to the release proposal at #22040 |
It's probably worth a sentence in the notable changes. Could someone help me write it? |
Since this is already released, reverting it would just make a bad situation worse. SEMVER was already broken once with the initial release, reverting it would just break it again. |
I've added this back to the TSC agenda to discuss in today's meeting. |
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.
+1 reverting is the right move. This is something we should fix before LTS
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
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.
I feel the conflict here is which of the following we want to make migration from easier:
- Earlier v10.x versions
- Versions older than v10.x
Since v10.x is an LTS version, but we haven't reached LTS stage, there's still a lot of life remaining in v10.x as folks try to update to v10.x from versions older than v10.x.
It's a sucky situation, but I'm on the side of 👍 on this PR as well.
This reverts a commit that accidentally introduced a semver-major change to Node 10 and broke userland code. A subsequent fix to that change and documentation change are reverted with it. Revert "http: fix res emit close before user finish" This reverts commit 2a9c833. Revert "http: always emit close on req and res" This reverts commit 8029a24. Revert "doc: fix HTTP req/res 'close' description" This reverts commit 8ab7ea6. PR-URL: #21809 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]>
Squashed and landed in 8799f43 |
This also reverts 2a9c833 which modifies the added file and line.
Refs: #20611 (comment)
/cc @nodejs/tsc
The change landed in v10.2.0. I suppose there is a risk to break code that is now relying on it?
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes