Repository navigation
fix(solana): retry Helius 429 once per fetch - #284
Merged
Merged
Conversation
zmaslerdev
changed the title
zmaslerdev
changed the title
Vinsho
self-requested a review
September 11, 2026 11:08
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.
A Helius HTTP 429 during a Solana balance fetch gets one retry of the same RPC body, request ID, and cursor after a fixed 1.1-second wait. One allowance is shared across the entire fetch, including token calls, DAS chunks, and staking pages, and is isolated from overlapping fetches. Standalone coin metadata lookup also gets one allowance.
Retry-Afteris absent or contains0or1; other values, including HTTP dates, follow existing error handling without a retry.Validation: 419 passed, 83 integration tests deselected on Python 3.12 after merging current master. Regression tests were observed failing before the fixes. Coverage includes retry success across RPC methods and a later staking page, identical request replay, one allowance across multiple errors and subsequent fetch reset, non-Helius/non-429 exclusion, and Retry-After guards. An independent mocked probe also verified overlapping fetches on one instance. Black 24.1.1, isort 5.13.2, and diff checks passed.