Repository navigation
feat(soroban): enforce RPC timeout and bounded retry wrapper (#1276) - #2089
Open
huangji6693-max wants to merge 1 commit into
Open
huangji6693-max wants to merge 1 commit into
huangji6693-max wants to merge 1 commit into
Conversation
…-blind submission (Arena1X#1276)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch had an error being deployed
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.
Closes #1276
Summary
SOROBAN_RPC_TIMEOUT_MS, default 10,000ms) and bounded retry wrapper (SOROBAN_RPC_MAX_RETRIES, default 2, with configurableSOROBAN_RPC_RETRY_BASE_DELAY_MS, default 250ms) across outbound Soroban RPC operations inSorobanService(backend/src/soroban/soroban.service.ts), includingpauseMarketandresumeMarketon-chain confirmation flows.SOROBAN_RPC_MAX_RETRIEStimes on timeout/connection errors with exponential backoff, while transaction submissions never blind-retry and always verifygetTransaction(txHash)before any resend.SorobanUnavailableErrorwhen RPC retries are exhausted so callers can distinguish RPC outages from contract-level permanent failures (SorobanPermanentError).SOROBAN_RPC_TIMEOUT_MS,SOROBAN_RPC_MAX_RETRIES, andSOROBAN_RPC_RETRY_BASE_DELAY_MSinbackend/.env.example.backend/src/soroban/soroban.service.spec.tscovering read timeout retry recovery, exhausted retrySorobanUnavailableErrorpropagation, and non-blind transaction submission under timeout.Verification
npx jest src/soroban/(2/2 test suites passed, 31/31 tests passed)