You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output of bun run bun:test, output of the cancel ReadableStreamBYOBReader test:
Reading from ReadableStreamBYOBReader...
Cancelling reader...
Stream was canceled: Canceling the reader while reading.
error: Test "cancel ReadableStreamBYOBReader" timed out after 5000ms
✗ Cancel async read operation on ReadableStream > cancel ReadableStreamBYOBReader [5000.13ms]
1 pass
1 fail
Ran 2 tests across 1 files. [5.02s]
error: script "bun:test" exited with code 1
What version of Bun is running?
1.2.2+c1708ea6a
What platform is your computer?
Linux 6.11.11-300.fc41.x86_64 x86_64 unknown
What steps can reproduce the bug?
While in a pending read() operation on a ReadableStreamBYOBReader, aborting the ReadableStreamBYOBReader does not interrupt the read operation.
I have created a repository to reproduce the issue: https://github.com/Borewit/bun-abort-ReadableStreamBYOBReader-read
Bun test can the executed by:
Same tests can be executed by Node.js:
What is the expected behavior?
I expect when a pending read() operation on a ReadableStreamBYOBReader to resolve with result
{done: true, value: undefined}
when cancel() is called.Output of
bun run bun:test
, output of the cancel ReadableStreamBYOBReader test:What do you see instead?
ReadableStreamBYOBReader read() hangs waiting for the promise to be resolved.
Output running both tests with Node.js:
Additional information
No response
The text was updated successfully, but these errors were encountered: