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
{{ message }}
Repository navigation
stream/iter merge() can hang when aborted during pending multi-source read #64012
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
The pending iterator.next() should reject, likely with AbortError, after the signal is aborted.
What do you see instead?
The script prints hung.
The multi-source merge() path waits on an internal promise while source reads are pending, but aborting the signal does not resolve that waiter. Since no source settles, the next abort check is never reached.
Activity
stream: fix merge abort for pending sources
stream: fix merge abort for pending sources
stream: fix merge abort for pending sources
stream: fix merge abort for pending sources