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: unify writableErrored and readableErrored #40799

Closed
wants to merge 2 commits into from

Conversation

ronag
Copy link
Member

@ronag ronag commented Nov 13, 2021

Both of these should always refer to the same error, hence there is no reason to separate them.

Refs: #40696

Both of these should always refer to the same error, hence
there is no reason to separate them.
@ronag ronag added the stream Issues and PRs related to the stream subsystem. label Nov 13, 2021
@ronag ronag requested a review from mcollina November 13, 2021 12:43
@ronag
Copy link
Member Author

ronag commented Nov 13, 2021

@nodejs/streams

@nodejs-github-bot nodejs-github-bot added the needs-ci PRs that need a full CI run. label Nov 13, 2021
@mscdex mscdex added the semver-major PRs that contain breaking changes and should be released in the next major version. label Nov 13, 2021
@@ -621,7 +621,7 @@ added:
Number of times [`writable.uncork()`][stream-uncork] needs to be
called in order to fully uncork the stream.

##### `writable.writableErrored`
##### `writable.errored`
Copy link
Member

Choose a reason for hiding this comment

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

needs changes: entries?

Copy link
Member Author

Choose a reason for hiding this comment

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

These props have never made it to any release... is that really necessary?

@@ -1239,7 +1239,7 @@ ObjectDefineProperties(Readable.prototype, {
}
},

readableErrored: {
errored: {
Copy link
Member

Choose a reason for hiding this comment

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

Do the readableErrored and writableErrored need to go through a deprecation cycle first? Those should likely be runtime deprecated aliases, yes?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not really. They haven’t been in any release.

@lpinca lpinca removed the semver-major PRs that contain breaking changes and should be released in the next major version. label Nov 13, 2021
@lpinca
Copy link
Member

lpinca commented Nov 13, 2021

I've remove the semver-major label as per #40799 (comment).

@ronag ronag added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Nov 13, 2021
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

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

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

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@ronag
Copy link
Member Author

ronag commented Nov 18, 2021

Landed in 340b770

@ronag ronag closed this Nov 18, 2021
ronag added a commit that referenced this pull request Nov 18, 2021
Both of these should always refer to the same error, hence
there is no reason to separate them.

PR-URL: #40799
Refs: #40696
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
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. needs-ci PRs that need a full CI run. stream Issues and PRs related to the stream subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants