Skip to content

Read an HTTP 429 that ethers gave up on as a rate limit - #330

Merged
RunTimeAdmin merged 1 commit into
mainfrom
fix/escalated-429
Nov 16, 2026
Merged

RunTimeAdmin merged 1 commit into
mainfrom
fix/escalated-429

Conversation

@RunTimeAdmin

Copy link
Copy Markdown
Owner

Follow-up to #329. Its first epoch on the checker (01:19 UTC) still left 2 agents unread, both with exceeded maximum retry limit.

That is how ethers reports an HTTP 429 once its attempts run out. rpc-provider.js allows one, so every 429 arrives that way, and the 429 survives only in the status of the response ethers escalated (CLIENT ESCALATED SERVER ERROR (429 Too Many Requests; exceeded maximum retry limit)). isRateLimited read only the short message, so those reads kept the short schedule. #329's tests built the error by hand with "429" in its words, which is why they did not catch this.

What changes (read-retry.js)

isRateLimited also reads the escalated response's status, and treats "exceeded maximum retry limit" as a rate limit. ethers says that only when its throttle retries run out.

Tests

rpc-provider.test.js drives a real HTTP 429 through rpcProvider from a local endpoint. The read must be classed as a rate limit and tried 7 times. It fails on main, and rpc-provider.test.js and chain.test.js pass (69). Oracle tests: 1,546; CI runs the full suite.

Deploy

Both operators.

🤖 Generated with Claude Code

ethers, allowed one try by rpc-provider.js, reports a 429 as "exceeded maximum retry limit", and the 429 is left only
in the status of the response it escalated. isRateLimited read the short message alone, so the checker's node, which
answers a burst with a 429, still got four quick tries: its first epoch on #329 left 2 agents unread with exactly that
error. It now reads the escalated status, and the words ethers uses. A test drives a real 429 through the provider.

Oracle tests: 1546.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RunTimeAdmin
RunTimeAdmin merged commit 2ed3453 into main Nov 16, 2026
7 checks passed
@RunTimeAdmin
RunTimeAdmin deleted the fix/escalated-429 branch November 16, 2026 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant