stream: fix async iterator destroyed error propagation #31700
Closed
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.
NOTE: It should now be safe to re-apply d15b8ea which was reverted in 2cd9892 due to a breaking regression which now is resolved through d016b9d
There was an edge case where if _destroy calls the error callback
later than one tick the iterator would complete early and not
propgate the error.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes