Gemini CLI Fix: Handle 429 Rate Limit Errors with Retries
ashmita-web · ghdev · 2026-08-19
This PR fixes an issue where the withEvalRetries helper in Gemini CLI silently missed 429 rate-limit and quota-exhaustion errors. Previously, a RESOURCEEXHAUSTED error would propagate as an uncaught failure, blocking PRs and nightly runs unnecessarily instead of being treated as a transient API hiccup.
Key Changes:
- Extended getApiErrorCode() to detect 429 patterns (e.g., RESOURCEEXHAUSTED, Too Many Requests).
- Updated reliability logging to retry or skip rate-limit errors, consistent with existing 500/503 handling.
- Added unit tests covering the "retry-then-skip" behavior on permanent 429s and recovery scenarios.
More from coding & agent
- Apple code signing drags for hours; official advice: just wait a week — pjausovec · 2026-10-16
- Hermes: a 4B model with 8K context got worse with more test-time compute, pointing to contextual reasoning — mangahomanga · 2026-10-16
- Flux 3 Klein's Default Templates Are Broken Without Its Prompt Upscaler — StrictMove5839 · 2026-10-16
- 21-person team ships hundreds of PRs weekly with AI writing 97% of the code — rseroter · 2026-10-16
- ClosedMCP: Set Up MCP Servers Once, Share Them Across Your Whole Team — Ok_Sprinkles1301 · 2026-10-16
- Heisentools: let an agent rewrite a mock.py until it mirrors any real tool's API — kieranklaassen · 2026-10-16