-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
pipeline()
doesn't finish with sandwiched duplex stream
#43682
Labels
stream
Issues and PRs related to the stream subsystem.
Comments
@nodejs/streams |
ronag
added a commit
to nxtedition/node
that referenced
this issue
Jul 6, 2022
If the destination stream is closed before the source has completed the pipeline should finnish with premature close. Fixes: nodejs#43682
ronag
added a commit
to nxtedition/node
that referenced
this issue
Jul 6, 2022
If the destination stream is closed before the source has completed the pipeline should finnish with premature close. Fixes: nodejs#43682
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
18.4.0
Platform
Linux & Microsoft Windows NT 10.0.19044.0 x64
Subsystem
stream
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
Not necessarily in that order.
What do you see instead?
Additional information
The writable side of the
local
Duplex stream finishes, but the readable side does not. I can see two arguments here, for deciding whether this is a bug in core.local
stream has disconnected readable and writable sides, that stream is responsible for destroying itself and/or ending its readable side.local
stream is being piped to the now-closedremote
stream, so it's a dead end. It'd be a different story forpipeline(x, local)
, i.e.local
being the last stream, because then the pipeline isn't consuming the readable side oflocal
. But inpipeline(x, local, x)
I expect the pipeline to fully manage the lifetime oflocal
.Last version where it works is 12.22.9 (or
readable-stream@3
). On 14.0.0, 16.14.2, 18.4.0, orreadable-stream@4
, it does not.The text was updated successfully, but these errors were encountered: