Skip to content

Conversation

@jacob314
Copy link
Contributor

@jacob314 jacob314 commented Feb 9, 2026

Summary

Fixes #18621

To Repro, auth with google and verify things work.
We should also rollback on the backend.

@jacob314 jacob314 requested a review from a team as a code owner February 9, 2026 18:27
@gemini-cli
Copy link
Contributor

gemini-cli bot commented Feb 9, 2026

Hi @jacob314, 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!

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jacob314, 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 focuses on improving the resilience and stability of the code assist converter by making its fromGenerateContentResponse function more robust. It introduces explicit checks for potentially missing or undefined properties within the input response object, such as the main response field and the candidates array. This ensures that the conversion process can proceed without errors, even when dealing with unexpected or incomplete data structures, thereby enhancing the overall reliability of the code assist feature.

Highlights

  • Robustness Improvement: The fromGenerateContentResponse function has been enhanced to gracefully handle cases where the response property or candidates array might be missing or undefined in the input CaGenerateContentResponse object.
  • Error Prevention: This change prevents potential runtime errors by ensuring that the candidates property is always initialized as an array, even when the source data is incomplete or malformed.
  • New Test Coverage: A new unit test has been added to specifically validate the function's ability to handle missing response properties, ensuring the converter's resilience.
Changelog
  • packages/core/src/code_assist/converter.test.ts
    • Added a new test case to verify that fromGenerateContentResponse handles a missing response property gracefully, setting responseId and an empty candidates array.
  • packages/core/src/code_assist/converter.ts
    • Modified fromGenerateContentResponse to check if res.response exists before accessing its properties. If res.response is missing, candidates is initialized as an empty array.
    • Updated the assignment of out.candidates to use the nullish coalescing operator (?? []) to ensure it is always an array, even if inres.candidates is undefined.
    • Reordered the assignment of out.responseId to occur earlier in the function for consistency.
Activity
  • No activity has been recorded for this pull request yet.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@jacob314 jacob314 enabled auto-merge February 9, 2026 18:29
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request hardens the fromGenerateContentResponse function in the code assist converter to gracefully handle malformed API responses where the response field might be missing. This is a good improvement that prevents potential runtime errors. A new unit test is also added to verify this behavior. I have one suggestion to further simplify the implementation for better readability and maintainability.

Comment on lines +139 to 147
if (!inres) {
out.candidates = [];
return out;
}
out.candidates = inres.candidates ?? [];
out.automaticFunctionCallingHistory = inres.automaticFunctionCallingHistory;
out.promptFeedback = inres.promptFeedback;
out.usageMetadata = inres.usageMetadata;
out.modelVersion = inres.modelVersion;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

While the current implementation is correct, it can be simplified by removing the conditional branch and early return. Using optional chaining (?.) for all property assignments from inres would make the code more concise, readable, and create a single execution path. This reduces complexity and makes the function easier to maintain and less prone to errors in future modifications.

Suggested change
if (!inres) {
out.candidates = [];
return out;
}
out.candidates = inres.candidates ?? [];
out.automaticFunctionCallingHistory = inres.automaticFunctionCallingHistory;
out.promptFeedback = inres.promptFeedback;
out.usageMetadata = inres.usageMetadata;
out.modelVersion = inres.modelVersion;
out.candidates = inres?.candidates ?? [];
out.automaticFunctionCallingHistory = inres?.automaticFunctionCallingHistory;
out.promptFeedback = inres?.promptFeedback;
out.usageMetadata = inres?.usageMetadata;
out.modelVersion = inres?.modelVersion;

@github-actions
Copy link

github-actions bot commented Feb 9, 2026

Size Change: +67 B (0%)

Total Size: 23.9 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 23.8 MB +67 B (0%)
./bundle/sandbox-macos-permissive-closed.sb 1.03 kB 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-closed.sb 3.29 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B

compressed-size-action

@gemini-cli gemini-cli bot added priority/p0 Critical and urgent (e.g., critical security vulnerability, major breakage). area/agent Issues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality labels Feb 9, 2026
Copy link
Member

@gundermanc gundermanc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Validated that it works with my repro.

@jacob314 jacob314 added this pull request to the merge queue Feb 9, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Feb 9, 2026
@jbianchini-peya
Copy link

image

@jacob314 jacob314 added this pull request to the merge queue Feb 9, 2026
Merged via the queue into main with commit 07056c8 Feb 9, 2026
29 checks passed
@jacob314 jacob314 deleted the fix_crash branch February 9, 2026 21:05
@skeshive
Copy link
Contributor

skeshive commented Feb 9, 2026

/patch stable

@github-actions
Copy link

github-actions bot commented Feb 9, 2026

Patch workflow(s) dispatched successfully!

📋 Details:

  • Channels: stable
  • Commit: 07056c8f16a9340aedcc716a5c247da07c135cf2
  • Workflows Created: 1

🔗 Track Progress:

@skeshive
Copy link
Contributor

skeshive commented Feb 9, 2026

/patch preview

@github-actions
Copy link

github-actions bot commented Feb 9, 2026

Patch workflow(s) dispatched successfully!

📋 Details:

  • Channels: preview
  • Commit: 07056c8f16a9340aedcc716a5c247da07c135cf2
  • Workflows Created: 1

🔗 Track Progress:

github-actions bot pushed a commit that referenced this pull request Feb 9, 2026
@github-actions
Copy link

github-actions bot commented Feb 9, 2026

🚀 Patch PR Created!

📋 Patch Details:

📝 Next Steps:

  1. Review and approve the hotfix PR: #18671
  2. Once merged, the patch release will automatically trigger
  3. You'll receive updates here when the release completes

🔗 Track Progress:

github-actions bot pushed a commit that referenced this pull request Feb 9, 2026
@github-actions
Copy link

github-actions bot commented Feb 9, 2026

🚀 Patch PR Created!

📋 Patch Details:

📝 Next Steps:

  1. Review and approve the hotfix PR: #18672
  2. Once merged, the patch release will automatically trigger
  3. You'll receive updates here when the release completes

🔗 Track Progress:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/agent Issues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality priority/p0 Critical and urgent (e.g., critical security vulnerability, major breakage).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API Error: Cannot read properties of undefined (reading 'candidates')

4 participants