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
- Agentic coding accessibility will reshape understanding of software complexity — pixlpa · 2026-08-24
- Devin Agent bypasses Slack block by finding emails in git logs — sandylikesfrogs · 2026-08-24
- Developer habits shift: Agents become collaborators from simple tools — latticecut · 2026-08-24
- Dev bottleneck shifts from writing to reading code: exe.dev co-founder — thursdai_pod · 2026-08-24
- The biggest AI mistake: trying to reinvent the wheel instead of using tools — Tired40s · 2026-08-24
- DeepPaperNote turns research papers into Obsidian notes — tom_doerr · 2026-08-24