[Vibecoded] Add RPC retry with exponential backoff and shared cooldown#1059
Open
rappie wants to merge 1 commit intoargotorg:mainfrom
Open
[Vibecoded] Add RPC retry with exponential backoff and shared cooldown#1059rappie wants to merge 1 commit intoargotorg:mainfrom
rappie wants to merge 1 commit intoargotorg:mainfrom
Conversation
When multiple workers hit RPC rate limits, requests now retry with exponential backoff (500ms-8s) and jitter. A shared cooldown IORef in Session coordinates workers so they back off together. - Add rpcThrottle field to Session - Add withRetry/fetchWithRetry wrapping fetchWithSession - Update all 4 internal call sites to use fetchWithRetry - Re-throw async exceptions (Timeout, ThreadKilled) correctly - RPC-level errors (Left) pass through without retry - Debug logging gated behind conf.debug, matching existing style Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator
|
@blishko maybe you could also have a look and if you find it good, merge? |
Collaborator
|
Maybe @gustavo-grieco or @elopez could take a look? |
Author
Yes. I have tested this by using Echidna. |
Collaborator
|
I will take a look to this soon |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WARNING: this is 100% vibecoded.
I've been using this without issue for several days.
Description
When multiple workers hit RPC rate limits concurrently, requests now
retry with exponential backoff (500ms–8s) and jitter. A shared
cooldown
IORefonSessioncoordinates workers so that once anyworker trips a rate limit, the others back off together instead of
hammering the endpoint independently.
Changes:
rpcThrottle :: IORef (Maybe UTCTime)toSessionwithRetry/fetchWithRetrywrappingfetchWithSessionfetchWithRetryTimeout,ThreadKilled); only retrysynchronous ones (network errors, HTTP 429, etc.)
Lefterrors pass through without retryconf.debug, matching existing styleChecklist