| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This reverts commit 0857790.
|
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). |
Sorry, something went wrong.
|
/cc @nodejs/streams |
Sorry, something went wrong.
|
I’m -1 to land this on master. I’m +1 to land this on node 10.0.0. |
Sorry, something went wrong.
|
/cc @nodejs/collaborators |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
|
@mcollina I'm confused a bit with your explicit approval. Does that mean you are no longer -1 on landing this on master? |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
This reverts commit 8f6ab9f. This PR adds _readableState.errorEmitted and add the tracking of it. Fixes: nodejs#6083 See: nodejs#20334 See: nodejs#20449
| Back | FazBrowse Home | New Git URL |
Fixes: #20334
CI: https://ci.nodejs.org/job/node-test-pull-request/14609/
Checklist