You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4a37ae9
Browse filesBrowse the repository at this point in the historyBrowse files
fix(rerank): back off between retries instead of spinning
All three rerank providers retried 429 and 5xx responses with a bare
`continue`, so the entire retry budget was spent within milliseconds of
the first rejection. That is useless against a per-minute quota, which
is exactly what hosted rerank endpoints enforce: the caller burns three
attempts and still fails, while the window it needed to wait out had
barely started.
Observed while driving the LoCoMo agentic suite against a hosted rerank
endpoint — search requests failed outright with RerankServiceError while
the endpoint itself was healthy and merely pacing us.
Adds `_errors.backoff_sleep()` (exponential with full jitter, capped at
8s) and wires it into the vLLM, DeepInfra and DashScope retry loops. The
jitter keeps a batch of concurrent searches from re-colliding after they
trip the limit together. No behaviour change when the endpoint is
healthy: the sleep only runs on a retryable failure that will be retried.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments