fix(provider-utils): make ReadableStream.cancel() properly finalize async iterators #9834
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.
Background
convertAsyncIteratorToReadableStreamdidn't notify its source when a consumer calledcancel(). This left async generators running even after the stream was cancelled.This affects any code that adapts
convertAsyncIteratorToReadableStream, e.g. LlamaIndex adapterManual Verification
Checked a real streaming flow (OpenAI via LlamaIndex): read a few chunks, then cancel. Next read returns done=true and no further chunks are produced.
Summary
convertAsyncIteratorToReadableStreamto properly calliterator.return()when the stream is cancelledChecklist