FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Revert "stream: prevent 'end' to be emitted after 'error'" by mscdex · Pull Request #20449 · nodejs/node · GitHub

/ node Public

Revert "stream: prevent 'end' to be emitted after 'error'" - #20449

Closed
mscdex wants to merge 1 commit into
nodejs:masterfrom
mscdex:revert-20104
Closed

Revert "stream: prevent 'end' to be emitted after 'error'"#20449
mscdex wants to merge 1 commit into
nodejs:masterfrom
mscdex:revert-20104

Conversation

mscdex commented May 1, 2018
edited
Loading

Copy link
Copy Markdown
Contributor

Fixes: #20334

CI: https://ci.nodejs.org/job/node-test-pull-request/14609/

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

nodejs-github-bot added the stream Issues and PRs related to the stream subsystem. label May 1, 2018

mscdex commented May 1, 2018
edited
Loading

Copy link
Copy Markdown
Contributor Author

FWIW I'm targeting master here because I think we need a better plan on how to more easily transition existing code (e.g. replacing existing uses of 'end' with some other event that acts as a "error or not" end event, such as 'close' or similar as I suggested in the referenced issue).

mscdex commented May 1, 2018

Copy link
Copy Markdown
Contributor Author

/cc @nodejs/streams

mcollina commented May 1, 2018

Copy link
Copy Markdown
Member

I’m -1 to land this on master. I’m +1 to land this on node 10.0.0.

mscdex commented May 4, 2018

Copy link
Copy Markdown
Contributor Author

/cc @nodejs/collaborators

mcollina 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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM, I'll redo the PR.

Ref: #20503.

BridgeAR added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label May 5, 2018

addaleax commented May 6, 2018
edited
Loading

Copy link
Copy Markdown
Member

@mcollina I’d really really like to not get in a habit of reverting commits only on release branches – if there is breakage that is significant enough to revert something, then we should try to keep master clear of that as well imo.

Edit: Removing the author ready label because there was a -1 on landing this on its target branch.

addaleax removed the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label May 6, 2018

mscdex commented May 7, 2018

Copy link
Copy Markdown
Contributor Author

@mcollina I'm confused a bit with your explicit approval. Does that mean you are no longer -1 on landing this on master?

mcollina commented May 7, 2018

Copy link
Copy Markdown
Member

Yes exactly. I’ll resend the PR as soon as this land, but we need to revert it in 10 (it seems this causes some other issues). I agree this was rushed in.

addaleax added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label May 7, 2018

addaleax commented May 7, 2018

Copy link
Copy Markdown
Member

Landed in 8f6ab9f

addaleax closed this May 7, 2018
addaleax pushed a commit that referenced this pull request May 7, 2018
This reverts commit 0857790.

PR-URL: #20449
Fixes: #20334
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>

ronag commented May 7, 2018

Copy link
Copy Markdown
Member

@addaleax re-open open v11?

addaleax commented May 7, 2018

Copy link
Copy Markdown
Member

@ronag As I understand it, @mcollina said that he’d open another fix for the original issue. Re-opening PRs doesn’t work always well with our release tooling, unfortunately.

mcollina added a commit to mcollina/node that referenced this pull request May 7, 2018
This reverts commit 8f6ab9f.

This PR adds _readableState.errorEmitted and add the tracking of it.

Fixes: nodejs#6083
See: nodejs#20334
See: nodejs#20449

mcollina commented May 7, 2018

Copy link
Copy Markdown
Member

Done in #20571.

mscdex deleted the revert-20104 branch May 7, 2018 12:37
MylesBorins pushed a commit that referenced this pull request May 8, 2018
This reverts commit 0857790.

PR-URL: #20449
Fixes: #20334
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins mentioned this pull request May 8, 2018
MylesBorins pushed a commit that referenced this pull request May 8, 2018
This reverts commit 0857790.

PR-URL: #20449
Fixes: #20334
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins pushed a commit that referenced this pull request May 9, 2018
This reverts commit 0857790.

PR-URL: #20449
Fixes: #20334
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no outstanding review comments, and a CI started. stream Issues and PRs related to the stream subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants


Back | FazBrowse Home | New Git URL