-
Notifications
You must be signed in to change notification settings - Fork 29
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
pipeTo
with preventCancel: true
never settle if readable
doesn't produce new chunks
#118
Comments
Good catch! Indeed, the The polyfill waits for both reads and writes to finish before shutting down the pipe. However, the reference implementation and most browser implementations only wait until all writes have finished. Any read requests that have been started by the pipe but haven't finished yet are "silently" discarded. I think I did this because we had to ensure there were no more pending read requests before the shutdown process calls I'll look into it. 🕵️ |
Fixed in v4.0.0-beta.3 |
Repro
Expected
Microsoft Edge canary 103.0.1255.0, with native
ReadableStream
andWritableStream
Node.js v16.13.1, with
stream/web
Actual
web-streams-polyfill: 4.0.0-beta.2
The text was updated successfully, but these errors were encountered: