Skip to content

Conversation

@sehoon38
Copy link
Collaborator

@sehoon38 sehoon38 commented Dec 29, 2025

…delay time

Summary

Perform exponential back-off retries with jitter for retryable error that doesn't have a specified delay time.

Details

When a retryable error is returned without a specified delay, we currently default to a fixed retry interval. This implements exponential backoff to increase the likelihood of success and prevent overwhelming the server.

Related Issues

#15481

How to Validate

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @sehoon38, 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 introduces a significant improvement to how retryable Google API quota errors are handled, particularly when no specific retry delay is provided by the API. Previously, a fixed 5-second delay was applied, which could be inefficient or contribute to server overload. The changes remove this fixed default, allowing the system to leverage an exponential back-off strategy with jitter. This approach dynamically increases retry intervals, enhancing system resilience, preventing overwhelming the server with repeated requests, and ultimately improving the success rate of operations encountering temporary quota limits.

Highlights

  • Flexible Retry Delays: The system no longer enforces a fixed 5-second default retry delay for generic retryable quota errors, allowing RetryableQuotaError instances to be created without a specified delay.
  • Enabling Exponential Back-off: By making the retryDelayMs property optional in RetryableQuotaError, the underlying retry mechanism can now implement an exponential back-off strategy with jitter for errors that do not provide a specific retry duration.
  • Refined Error Classification: The classifyGoogleError function has been updated to no longer assign a default 5-second retry delay to generic 429 errors, aligning with the new flexible retry delay approach.
  • Test Suite Alignment: Unit tests for googleQuotaErrors were updated to reflect these changes, ensuring that generic 429 errors are correctly classified without a predefined retry delay.

🧠 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 implements exponential backoff for retryable errors that do not specify a retry delay, which is a good improvement over the previous fixed delay. The changes correctly adapt RetryableQuotaError to have an optional retry delay. My review identifies one high-severity issue in the retry logic where a retry delay of 0ms would be handled incorrectly, causing an unnecessary wait instead of an immediate retry. I've provided a suggestion to fix this.

@github-actions
Copy link

Size Change: +176 B (0%)

Total Size: 22 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 22 MB +176 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 marked this pull request as ready for review December 29, 2025 21:15
@sehoon38 sehoon38 requested a review from a team as a code owner December 29, 2025 21:15
constructor(
message: string,
override readonly cause: GoogleApiError,
retryDelayMs?: number,
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this should've been seconds, not ms

@sehoon38 sehoon38 added this pull request to the merge queue Dec 29, 2025
Merged via the queue into main with commit 07e597d Dec 29, 2025
32 of 33 checks passed
@sehoon38 sehoon38 deleted the sehoon/exponential_backoff branch December 29, 2025 22:29
@sehoon38
Copy link
Collaborator Author

/patch

@github-actions
Copy link

Patch workflow(s) dispatched successfully!

📋 Details:

  • Channels: stable,preview
  • Commit: 07e597de403053fc341a5120e29bf82ae46035eb
  • Workflows Created: 2

🔗 Track Progress:

github-actions bot pushed a commit that referenced this pull request Dec 30, 2025
@github-actions
Copy link

🚀 Patch PR Created!

📋 Patch Details:

📝 Next Steps:

  1. ⚠️ Resolve conflicts in the hotfix PR first: #15733
  2. Test your changes after resolving conflicts
  3. Once merged, the patch release will automatically trigger
  4. You'll receive updates here when the release completes

🔗 Track Progress:

github-actions bot pushed a commit that referenced this pull request Dec 30, 2025
@github-actions
Copy link

🚀 Patch PR Created!

📋 Patch Details:

📝 Next Steps:

  1. ⚠️ Resolve conflicts in the hotfix PR first: #15734
  2. Test your changes after resolving conflicts
  3. Once merged, the patch release will automatically trigger
  4. You'll receive updates here when the release completes

🔗 Track Progress:

@github-actions
Copy link

🚀 Patch Release Started!

📋 Release Details:

  • Environment: prod
  • Channel: preview → publishing to npm tag preview
  • Version: v0.23.0-preview.3
  • Hotfix PR: Merged ✅
  • Release Branch: release/v0.23.0-preview.3-pr-15684

⏳ Status: The patch release is now running. You'll receive another update when it completes.

🔗 Track Progress:

@github-actions
Copy link

🚀 Patch Release Started!

📋 Release Details:

  • Environment: prod
  • Channel: stable → publishing to npm tag latest
  • Version: v0.22.4
  • Hotfix PR: Merged ✅
  • Release Branch: release/v0.22.4-pr-15684

⏳ Status: The patch release is now running. You'll receive another update when it completes.

🔗 Track Progress:

@github-actions
Copy link

Patch Release Complete!

📦 Release Details:

  • Version: 0.22.5
  • NPM Tag: latest
  • Channel: stable
  • Dry Run: false

🎉 Status: Your patch has been successfully released and published to npm!

📝 What's Available:

🔗 Links:

@github-actions
Copy link

Patch Release Complete!

📦 Release Details:

🎉 Status: Your patch has been successfully released and published to npm!

📝 What's Available:

🔗 Links:

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