-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Call push
asyncly after readableStream.on('data', ...)
will cause error.
#38865
Labels
stream
Issues and PRs related to the stream subsystem.
Comments
07akioni
changed the title
Call push async after
Call push async after May 31, 2021
readStream.on('data)
will cause error.readStream.on('data', ...)
will cause error.
cc @nodejs/streams |
07akioni
changed the title
Call push async after
Call push async after May 31, 2021
readStream.on('data', ...)
will cause error.readableStream.on('data', ...)
will cause error.
07akioni
changed the title
Call push async after
Call May 31, 2021
readableStream.on('data', ...)
will cause error.push
asyncly after readableStream.on('data', ...)
will cause error.
cc @nodejs/streams |
You need to implement the |
This is clearly documented. |
07akioni
added a commit
to 07akioni/vue-next
that referenced
this issue
Jun 1, 2021
…an empty _read method. Nor it will throw errors. See nodejs/node#38865. The tests passes in jest before because jest mock the global promise and causes inconsistant behavior compared with native nodejs. jestjs/jest#11497
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Everytimes.
What is the expected behavior?
I'm not quite sure but I won't expect it to have errors after reading the docs.
What do you see instead?
Additional information
The text was updated successfully, but these errors were encountered: