S3 - HTTP backend client: request timeout, retry, and abort support

[davedumto]

Summary

The HTTP backend client has no timeout handling, so a slow or hung gateway can hang the calling application indefinitely. Add configurable timeout, limited retry for idempotent reads, and abort support.

Context

The HTTP backend client wraps the wallet gateway routes. It currently issues fetch calls with no time bound and no cancellation.

Requirements

• Add a configurable per-request timeout with a sensible default. On timeout, reject with a typed error rather than hanging.
• Support an AbortSignal so callers can cancel in flight requests.
• Add limited retry with backoff for safe, idempotent read operations only. Never retry a submission or any state-changing call.
• Make timeout and retry counts configurable through the client options, with defaults that are safe for a browser.
• Tests covering: a slow response triggers the timeout error, an abort signal cancels the request, a read retries then succeeds, and a submission is never retried.

---

Before you start

Read the contributing guide first: https://github.com/Vellar-Wallet/vellar-sdk/blob/main/CONTRIBUTING.md

Key rules:

• Fork the repo and work from your fork. Never push to this repository directly.
• All pull requests must target the drips branch, never main. PRs opened against main are closed automatically.
• Only work on issues assigned to you. Comment on this issue to request assignment and wait before starting.

Run these locally before opening a PR (CI runs the same checks):

npm install
npm run typecheck
npm test
npm run build

New code is expected to come with tests.

Questions go to the Telegram group, not new issues: https://t.me/+RWPCKXXJTj45Njk0

[abuobakarserlis]

@abuobakarserlis has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi @maintainers,
I'd love to take this issue on. The core goal is clear, and I can deliver a clean, well-tested implementation that prioritizes backward compatibility and system performance.
I am ready to dive into the codebase right away—let me know if I can be assigned!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abuobakarserlis to this issue.

[ZeePearl56]

@ZeePearl56 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Kindly assign to me, pls.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ZeePearl56 to this issue.

[JohnOluB]

@JohnOluB has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’ll start by reviewing the HTTP client and contributing guide to understand the current fetch flow and request types. Then I’ll add configurable timeouts, AbortSignal support, and limited retries only for safe read requests, while making sure state changing requests are never retried.

I’ll also add tests for timeout, abort, successful read retries, and the no retry behavior for submissions.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JohnOluB to this issue.

[ayo-ola0710]

@ayo-ola0710 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer can i handle these for you pls

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayo-ola0710 to this issue.

[lukawisdom06]

@lukawisdom06 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi! I’d like to take this issue. I’ll go through the existing implementation, identify the root cause, and work on a clean solution before submitting a PR for review.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @lukawisdom06 to this issue.

[drips-wave]

Congratulations, @lukawisdom06! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @lukawisdom06: 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 🌊