fix(core): restrict "System: Please continue" invalid stream retry to Gemini 2 models#20897
Conversation
|
Hi there! Thank you for your contribution to Gemini CLI. To improve our contribution process and better track changes, we now require all pull requests to be associated with an existing issue, as announced in our recent discussion and as detailed in our CONTRIBUTING.md. This pull request is being closed because it is not currently linked to an issue. Once you have updated the description of this PR to link an issue (e.g., by adding How to link an issue: Thank you for your understanding and for being a part of our community! |
|
Hi @SandyTao520, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly restricts the InvalidStream retry mechanism to only apply to Gemini 2 models. The change in GeminiClient is straightforward, adding a check with isGemini2Model. The accompanying test updates are thorough, ensuring existing tests for the retry logic now use a Gemini 2 model, and a new test has been added to verify that non-Gemini 2 models correctly skip this retry logic. The changes are well-implemented and address the issue effectively.
|
Size Change: +6.55 kB (+0.03%) Total Size: 25.8 MB
ℹ️ View Unchanged
|
Summary
Restrict the
"System: Please continue."invalid stream retry to Gemini 2 models only. Non-Gemini-2 models (e.g., Gemini 3) no longer trigger this retry mechanism onInvalidStreamevents.Details
The
processTurnmethod inGeminiClientpreviously injected a"System: Please continue."message whenever anInvalidStreamevent was received andgetContinueOnFailedApiCall()was true, regardless of the model. This change adds anisGemini2Model(modelToUse)guard so the retry only fires for Gemini 2.x models.isGemini2Modelimport fromconfig/models.jsisGemini2Model(modelToUse)'gemini-2.0-flash'as the routed modelRelated Issues
#18007
How to Validate
npm test -w @google/gemini-cli-core -- src/core/client.test.tsshould recursively call sendMessageStream with "Please continue." when InvalidStream event is received for Gemini 2 modelsshould not retry with "Please continue." when InvalidStream event is received for non-Gemini-2 modelsshould stop recursing after one retry when InvalidStream events are repeatedly receivedPre-Merge Checklist