Fix regression: Errors not emitted in streams#14314
Merged
gaearon merged 1 commit intofacebook:masterfrom Nov 27, 2018
Merged
Conversation
Regression introduced in facebook#14182 resulted in errors no longer being emitted on streams, breaking many consumers. Co-authored-by: Elliot Jalgard <elliot.j@live.se>
gaearon
approved these changes
Nov 27, 2018
Collaborator
gaearon
left a comment
There was a problem hiding this comment.
I'm not deeply familiar with Node Readable API but base implementation is function (err, cb) { this.push(null); cb(err); }' so this looks good.
|
Hi, when will this change be released? |
Collaborator
|
If you need it urgently you can build React from master and get the fix. I can't give you an exact day — we generally release things when we feel they're stable, and this means giving some time for other changes to shake out. Probably within a few weeks. |
|
Thanks for your response Dan, we’ll build from the commit.
Elliott
Elliott Greaves
…Sent from my mobile
On 6 Dec 2018, at 16:07, Dan Abramov ***@***.***> wrote:
If you need it urgently you can build React from master and get the fix. I can't give you an exact day — we generally release things when we feel they're stable, and this means giving some time for other changes to shake out. Probably within a few weeks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Fix appears to be in 16.7.0 |
jetoneza
pushed a commit
to jetoneza/react
that referenced
this pull request
Jan 23, 2019
Regression introduced in facebook#14182 resulted in errors no longer being emitted on streams, breaking many consumers. Co-authored-by: Elliot Jalgard <elliot.j@live.se>
n8schloss
pushed a commit
to n8schloss/react
that referenced
this pull request
Jan 31, 2019
Regression introduced in facebook#14182 resulted in errors no longer being emitted on streams, breaking many consumers. Co-authored-by: Elliot Jalgard <elliot.j@live.se>
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
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regression introduced in #14182 resulted in errors no longer being emitted on streams, breaking consumers.
The cause is a faulty implementation of the
destroy()method ofReactMarkupReadableStream, which resulted in noerrorevent being thrown even though one expected it.This patch fixes that + adds tests for the fixes.