Repository navigation
fix: stop a hung RPC endpoint holding up reads - #738
Merged
MoonBoi9001 merged 1 commit intoOct 9, 2026
Conversation
Until 2 endpoints agree on the chain's newest block, a read first asks every endpoint for it. 1 endpoint that never answered held that read for the full request timeout, once a minute. Each ask now gives up after 3 seconds and the check goes on with the answers it has.
MoonBoi9001
marked this pull request as ready for review
October 9, 2026 15:56
MoonBoi9001
added this pull request to stack #741
October 9, 2026 17:57
MoonBoi9001
removed this pull request from stack #741
October 9, 2026 17:58
MoonBoi9001
added this pull request to stack #742
October 9, 2026 17:58
MoonBoi9001
removed this pull request from stack #742
October 9, 2026 17:58
MoonBoi9001
added this pull request to stack #743
October 9, 2026 17:58
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
1 participant
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.
Until 2 RPC endpoints agree on the chain's newest block, every read first asks each endpoint for it, so 1 endpoint that never answered held a read for the full request timeout once a minute. This gives each of those asks a 3 second limit, after which the check carries on with the endpoints that did answer.