Skip to content

http: don't emit error for stream destroyed - #33654

Closed
ronag wants to merge 3 commits into
nodejs:masterfrom
nxtedition:outgoing-error-close
Closed

http: don't emit error for stream destroyed#33654
ronag wants to merge 3 commits into
nodejs:masterfrom
nxtedition:outgoing-error-close

Conversation

@ronag

@ronagronag commented May 30, 2020

Copy link
Copy Markdown
Member

Aligns with streams

Refs: #33591

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

@ronagronag added http Issues or PRs related to the http subsystem. v14.x labels May 30, 2020
@ronag
ronag requested a review from addaleaxMay 30, 2020 08:41
@ronag
ronagforce-pushed the outgoing-error-close branch from 72c7eac to 734bf3aCompareMay 30, 2020 08:42
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@ronag

Copy link
Copy Markdown
MemberAuthor

@nodejs/http @nodejs/web-server-frameworks

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@BridgeAR
BridgeARforce-pushed the master branch 2 times, most recently from 8ae28ff to 2935f72CompareMay 31, 2020 12:18
@ronagronag changed the title http: don't emit error after closehttp: don't emit error for stream destroyedMay 31, 2020
@ronag
ronagforce-pushed the outgoing-error-close branch 2 times, most recently from b152c48 to a21385eCompareMay 31, 2020 19:14
@ronag

Copy link
Copy Markdown
MemberAuthor

unsure about the semversiness of this one.

@ronag
ronagforce-pushed the outgoing-error-close branch from a21385e to 48a58b1CompareMay 31, 2020 19:45
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Comment threadtest/parallel/test-http-server-write-end-after-end.js Outdated
@ronag
ronagforce-pushed the outgoing-error-close branch 2 times, most recently from 92d8ad6 to 73b6a74CompareJune 1, 2020 15:38
Comment threadtest/parallel/test-http-server-write-end-after-end.js Outdated
@BethGriggs

Copy link
Copy Markdown
Member

Should this land in the next v14.x release?

@ronag
ronag requested a review from mcollinaJune 9, 2020 15:30

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, crossing fingers we do not break anything.

@ronag
ronagforce-pushed the outgoing-error-close branch from 0d71e89 to 7191d18CompareJune 15, 2020 20:56
@ronag

Copy link
Copy Markdown
MemberAuthor

@mcollina: I've updated the test so that it doesn't have to be commented out. I don't think #33684 should be blocking this PR.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ronag
ronagforce-pushed the outgoing-error-close branch from 7191d18 to 402fc26CompareJune 20, 2020 11:58
@ronag

Copy link
Copy Markdown
MemberAuthor

This needs another CI run + CITGM

@addaleaxaddaleax added needs-ci PRs that need a full CI run. needs-citgm PRs that need a CITGM CI run. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. and removed v14.x needs-ci PRs that need a full CI run. needs-citgm PRs that need a CITGM CI run. labels Jun 20, 2020
@addaleax

Copy link
Copy Markdown
Member

@nodejs-github-bot

nodejs-github-bot commented Jun 21, 2020

Copy link
Copy Markdown
Collaborator

@ronag

Copy link
Copy Markdown
MemberAuthor

Landed in 30cc542

@ronagronag closed this Jun 21, 2020
ronag added a commit that referenced this pull request Jun 21, 2020
Refs: #33591
PR-URL: #33654
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
@MylesBorins

Copy link
Copy Markdown
Contributor

This doesn't land cleanly on v14.x. @ronag would you be willing to backport?

@targos

Copy link
Copy Markdown
Member

Should this be backported with #32933 ?

@ronag

Copy link
Copy Markdown
MemberAuthor

Yes. I'm a little overloaded at the moment though. If you need help ping me again in a. week :).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.httpIssues or PRs related to the http subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@ronag@nodejs-github-bot@BethGriggs@addaleax@MylesBorins@targos@mcollina@jasnell