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: pending next() hangs after iterator return() #63519
pendingNext should settle after await iter.return(), normally as { value: undefined, done: true } or a rejection, so no read promise is left unresolved.
What do you see instead?
push(): observed hang; expected pending next() to settle after return()broadcast(): observed hang; expected pending next() to settle after return()
pendingNext stays pending and the timeout wins, because next() stores a resolver for the empty read, but return() detaches/cleans up without resolving or rejecting that stored pending read.
Activity
trivikr commentedon May 28, 2026
The bug in push was fixed in #63555, when fixing for
iterator.throw()stream: settle pending broadcast reads on return
stream: settle pending broadcast reads on return
stream: settle pending broadcast reads on return