-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
stream.finished readonly doesn't fire if writable side is open #32965
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
This is because of |
4 tasks
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 21, 2020
If passed a Duplex where readable or writable has been explicitly disabled then don't assume 'close' will be emitted. Fixes: nodejs#32965
BethGriggs
pushed a commit
that referenced
this issue
Apr 27, 2020
If passed a Duplex where readable or writable has been explicitly disabled then don't assume 'close' will be emitted. Fixes: #32965 PR-URL: #32967 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Mathias Buus <mathiasbuus@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
BethGriggs
pushed a commit
that referenced
this issue
Apr 28, 2020
If passed a Duplex where readable or writable has been explicitly disabled then don't assume 'close' will be emitted. Fixes: #32965 PR-URL: #32967 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Mathias Buus <mathiasbuus@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
3 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
stream.finished(duplex, { readable: true, writable: false }, cb)
doesn't fire if writable side is finalising.The text was updated successfully, but these errors were encountered: