fix: prevent duplicate text emission in Gemini provider (fixes #9822) #9823
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.
This PR attempts to address Issue #9822. Feedback and guidance are welcome!
Problem
The Gemini provider was emitting duplicate text when streaming responses. This occurred when the API response chunks contained both
candidateswith structured content AND a fallbacktextproperty with the same content, causing the text to be yielded twice.Solution
Added a
processedContentflag to track whether any content was yielded from the structuredcandidatesprocessing. The fallback tochunk.textnow only occurs when no content was processed from candidates, preventing duplicate text emission.Changes
src/api/providers/gemini.tsto add duplicate prevention logicsrc/api/providers/__tests__/gemini.spec.tsto verify the fixTesting
Fixes #9822