Repository navigation
Add exponential backoff retry and Horizon error decoder in client.ts #974
Description
Description: Problem
- In
src/lib/client.ts(SorobanClient), RPC calls that encounter HTTP 429 (rate limited) or 503 (service unavailable) fail immediately without retrying. - Horizon error response parsing only extracts top-level
detailstrings, dropping criticalextras.result_codesoperation codes. - Missing test cases in
src/lib/__tests__/mock-client.test.tsasserting retry behavior during network dropouts.
Solution
Implement an automatic retry wrapper with exponential backoff and jitter for transient HTTP 429, 502, 503, and 504 errors. Parse and format extras.result_codes into actionable messages, and add unit tests verifying retry behavior.
Acceptance Criteria
- Transient RPC failures retry up to 3 times with exponential backoff.
- Horizon operation error codes (
op_underfunded,op_bad_auth) are parsed and exposed. - Mock client tests verify retry attempts and backoff timing in
src/lib/__tests__/mock-client.test.ts.
Note for Contributors
If you're assigned to this issue, write a clear and detailed description for your pull request. Explain what was changed, why it was needed, how it was implemented, and include any relevant testing or screenshots where applicable.
Activity
area523ufo commentedon Oct 15, 2026
Hi! I've submitted a fix with unit tests for this issue in PR #980. Please let me know if any adjustments are needed!
timmyp10111 commentedon Oct 15, 2026
@timmyp10111 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @timmyp10111 to this issue.
Jenola344 commentedon Oct 15, 2026
@Jenola344 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jenola344 to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @Jenola344! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Jenola344: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
drips-wave commentedon Oct 26, 2026
This issue has been completed by @Jenola344 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Jenola344: You earned 150 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.