Retry transient Ponder GraphQL network errors - #64
Merged
Conversation
The GetPositionsV2 sync job occasionally sees a "Premature close" from the indexer, consistent with a stale keep-alive socket being reused right as it's closed server-side. There was no retry for this case: network errors that couldn't fall back landed straight in the logs. Adds a RetryLink ahead of the HTTP link so transport-level failures get a few short, jittered retries before reaching the error/fallback handling. GraphQL-level errors are unaffected.
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.
Summary
GetPositionsV2query occasionally fails with a "Premature close" network error against the indexer's GraphQL endpoint — consistent with a stale keep-alive socket getting reused right as the server closes it.errorLinkonly retries by switching to a fallback URL when one is configured, otherwise the failure goes straight through.RetryLinkahead of the HTTP link so transport-level failures get a few short, jittered retries (max 3, 200ms–2s backoff) before reaching the existing error/fallback handling. GraphQL-level errors (a successful response with errors in it) are unaffected — only network/transport failures are retried.Test plan
nest buildpasseseslint/prettierclean on the changed file