Badri Narayanan S 0fa945b069 fix: don't count rate limit waits as failed retry attempts ...

When all accounts are rate-limited or token-exhausted, the retry loop
was incorrectly counting the wait time as a failed attempt. This caused
premature "Max retries exceeded" errors when we were just patiently
waiting for accounts to become available.

- Add attempt-- after sleeping for rate limits or strategy waits
- Add #diagnoseNoCandidates() to hybrid strategy for better logging
- Add getTimeUntilNextToken() and getMinTimeUntilToken() to token tracker
- Return waitMs from hybrid strategy when all accounts are token-blocked

Co-Authored-By: Claude <noreply@anthropic.com>

2026-01-23 14:29:24 +05:30

..

index.js

feat(webui): add subscription tier and quota visualization

2026-01-10 06:05:17 +08:00

message-handler.js

fix: don't count rate limit waits as failed retry attempts

2026-01-23 14:29:24 +05:30

model-api.js

feat: align project discovery with opencode-antigravity-auth reference

2026-01-19 14:21:30 +05:30

rate-limit-parser.js

fix: accurate quota reporting with project ID and improved rate limit handling

2026-01-15 16:18:13 +05:30

request-builder.js

fix: filter Antigravity system prompt from model responses

2026-01-09 14:10:41 +05:30

session-manager.js

refactor: Reorganize src/ into modular folder structure

2026-01-01 15:13:43 +05:30

sse-parser.js

fix: add image response support

2026-01-13 11:17:17 +08:00

sse-streamer.js

fix: preserve whitespace-only chunks in SSE stream (#139)

2026-01-17 12:16:28 +05:30

streaming-handler.js

fix: don't count rate limit waits as failed retry attempts

2026-01-23 14:29:24 +05:30