Open matthieusieben opened 1 month ago
Related issue: #55010 CC @nodejs/streams
I don't understand what the problem is.
Calling asyncGenerator.retrun()
should cause the readable to be destroyed, and Readable stream destroyed
to be printed. This is not the case. The pipeline callback function is never called either.
Sounds like a bug.
@matthieusieben would you like to send a PR to fix it?
I gave it a try but I struggle a bit.
Version
v22.9.0
Platform
Subsystem
stream
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Any code used as
Duplex.from(async function () {})
that does not fully consume the input will prevent the input stream to be properly disposed:What is the expected behavior? Why is that the expected behavior?
The readable's destroy steps should be called.
What do you see instead?
The readable is not destroyed.
Additional information
No response