Skip to content

Conversation

@gemini-cli-robot
Copy link
Collaborator

This PR automatically cherry-picks commit 9e6914d to patch version v0.21.2 in the stable release to create version 0.21.3.

@gemini-cli-robot gemini-cli-robot requested a review from a team as a code owner December 18, 2025 23:55
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @gemini-cli-robot, 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 error classification logic for Google API responses, specifically targeting HTTP 429 (Too Many Requests) errors. The primary goal is to ensure that any 429 error, regardless of its specific details, is recognized as a retryable quota error. This change introduces a default 5-second retry delay for generic 429s, making the system more robust in handling temporary rate limits and improving the overall reliability of interactions with Google services.

Highlights

  • Improved 429 Error Handling: All HTTP 429 (Too Many Requests) errors from Google APIs are now consistently classified as RetryableQuotaError.
  • Default Retry Delay: A default retry delay of 5 seconds is applied to 429 errors when no specific retry information is provided in the error details, enhancing resilience.
  • Enhanced Test Coverage: Existing tests were updated and new test cases were added to thoroughly validate the new fallback logic for handling generic 429 errors.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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 correctly implements a fallback mechanism to treat all unclassified Google API 429 errors as retryable, which is a good improvement for resilience. The accompanying tests are thorough and cover the new logic well. However, I've identified a significant code duplication in classifyGoogleError where the logic for creating the fallback RetryableQuotaError is repeated. I've left a comment with a suggestion to refactor this to improve code maintainability.

Comment on lines +250 to +264
// If we reached this point and the status is still 429, we return retryable.
if (status === 429) {
const errorMessage =
googleApiError?.message ||
(error instanceof Error ? error.message : String(error));
return new RetryableQuotaError(
errorMessage,
googleApiError ?? {
code: 429,
message: errorMessage,
details: [],
},
DEFAULT_RETRYABLE_DELAY_SECOND,
);
}
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This block of code for creating a fallback RetryableQuotaError is nearly identical to the one added at lines 117-129. The logic for defining errorMessage is also duplicated (see lines 100-102 and 252-254). This duplication increases maintenance overhead and the risk of future inconsistencies if the fallback logic needs to be changed.

To improve maintainability, I recommend refactoring to remove this duplication. You could either:

  1. Extract the creation of the default RetryableQuotaError into a small, private helper function.
  2. Restructure the classifyGoogleError function to have a single fallback path for all unclassified 429 errors at the end of the function.

@github-actions
Copy link

Size Change: +672 B (0%)

Total Size: 21.6 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 21.6 MB +672 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

@sehoon38 sehoon38 enabled auto-merge (squash) December 19, 2025 00:01
@sehoon38 sehoon38 merged commit d0cdeda into release/v0.21.2-pr-15288 Dec 19, 2025
19 checks passed
@sehoon38 sehoon38 deleted the hotfix/v0.21.2/0.21.3/stable/cherry-pick-9e6914d/pr-15288 branch December 19, 2025 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants