Repository navigation
Read an agent again once when the node refused its reads through every retry - #332
Merged
Merged
Conversation
…y retry At 02:34 UTC on 16 November 2026 the checker's node refused the guard step's first chunk of ten getIdentity reads for about 18 s. Nine got through within readWithBackoff's seven tries for a rate limit; one ran out, and the guard loop left its agent for the next epoch. An agent whose guard read is still refused now goes back on the end of the queue once, and is read again after the others and at least REREAD_PAUSE_MS (10 s) after the refusal. Agents whose batched first reads were refused are read once more after the same pause. Both come before anything is written for the agent, so nothing is repeated; refused again, it waits for the next epoch as before. The per-agent step after the guards, which writes, is unchanged. Three end-to-end tests run the real index.js against a stub that refuses chosen reads, as ethers reports a 429 it gave up on; all three fail on main. The harness takes a preload, and these tests load fast-retry.js to cut the epoch's pauses. Oracle tests: 1549. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
At 02:34 UTC on 16 November 2026, the checker's first hourly epoch on
2ed3453(#330) skipped agent0x31d08650withexceeded maximum retry limit. Its node,rpc.quicknode.testnet.arc.io, refused the guard step's first chunk of tengetIdentityreads for about 18 s (02:34:48 to 02:35:06). Nine got through withinreadWithBackoff's seven tries for a rate limit: 24 waits were over 2 s, so the long schedule ran. One ran out of tries. The guard loop logged it and moved on, so that agent waited an hour. Refund reads at 02:34:35 to 38 had drained the node's budget just before.What changes (
index.js,epoch-policy.js)getAgentInfoandisBonded, just before its write) is still refused with a transient error goes back on the end of the queue once. It is read again after the other agents, and at leastREREAD_PAUSE_MS(10 s) after the refusal. No chunk mixes first-pass agents with agents put back. One line is logged when an agent is put back.RATE_LIMIT_ATTEMPTSstays at 7.RPC_URLrow says this.Tests (
robustness.test.js)Three end-to-end tests run the real
index.jsagainst the stubbed chain. The stub has a new key,refusedReads, which refuses chosen reads of an agent the way ethers reports a 429 it gave up on.All three fail on main's
index.jsand pass here. The harness now takes apreloadlist, and these tests loadfast-retry.js, which cuts the epoch's pauses to milliseconds and leaves the epoch interval alone. Oracle tests: 1549, from one full run.Deploy
Both operators, checker first. The checker is the one that needs it.
🤖 Generated with Claude Code