Skip to content
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

stream: fix .end() error propagation #36817

Closed
wants to merge 4 commits into from

Conversation

ronag
Copy link
Member

@ronag ronag commented Jan 6, 2021

No description provided.

@ronag ronag added the stream Issues and PRs related to the stream subsystem. label Jan 6, 2021
@ronag ronag requested review from mcollina and lpinca January 6, 2021 18:46
@ronag ronag force-pushed the writable-end-error branch from 96a3e8f to db00cc2 Compare January 6, 2021 18:47
@ronag
Copy link
Member Author

ronag commented Jan 6, 2021

@nodejs/stream

@ronag ronag requested a review from lpinca January 6, 2021 19:52
@ronag ronag force-pushed the writable-end-error branch from e25f804 to 48ea4c2 Compare January 6, 2021 20:13
@ronag ronag force-pushed the writable-end-error branch from c8eb497 to 5443a22 Compare January 6, 2021 20:18
@ronag
Copy link
Member Author

ronag commented Jan 6, 2021

@lpinca: Though I agree that the behavior is a little strange and should be discussed I'm not sure it's relevant for this PR other than we noticed it with the tests added here.

@lpinca
Copy link
Member

lpinca commented Jan 6, 2021

I agree, I vaguely remember having already discussed it in an old PR (It was probably the PR calling all pending callbacks on error) but I may be wrong.

Copy link
Member

@lpinca lpinca left a comment

Choose a reason for hiding this comment

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

RSLGMT

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@ronag ronag added request-ci Add this label to start a Jenkins CI on a PR. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Jan 6, 2021
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jan 6, 2021
@nodejs-github-bot
Copy link
Collaborator

@ronag ronag added the request-ci Add this label to start a Jenkins CI on a PR. label Jan 9, 2021
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jan 9, 2021
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

ronag added a commit that referenced this pull request Jan 11, 2021
PR-URL: #36817
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@ronag
Copy link
Member Author

ronag commented Jan 11, 2021

Landed in a4fce32

@ronag ronag closed this Jan 11, 2021
danielleadams pushed a commit that referenced this pull request Jan 12, 2021
PR-URL: #36817
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@danielleadams danielleadams mentioned this pull request Jan 12, 2021
@mcollina mcollina added the semver-major PRs that contain breaking changes and should be released in the next major version. label Jan 25, 2021
@mcollina
Copy link
Member

mcollina commented Jan 25, 2021

mark this as semver-major post-release as it broke things in v15 :(, see #37027 for more details.

cc @nodejs/tsc

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 pending requests for changes, and a CI started. semver-major PRs that contain breaking changes and should be released in the next major version. stream Issues and PRs related to the stream subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants