stream: prevent dead lock when Duplex generator is "thrown" #56287
+63
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes regression introduced in #55096 and outlined in #56278.
When using a
for await
loop, v8 (?) might call the.throw
function of the iterable instead of the stream handlers (write
,final
,destroy
). This can cause a dead lock as this line waits for a promise that will never be resolved (since the promise is setteled from the stream handlers).This PR adresses that issue by making sure the promise is resolved whenever the generator's
return
andthrow
function are called, preventing the dead lock.cc @jakecastelli