akash-network / akash-network/console
console-web -> console-api network errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
What
Console-web encounters multiple types of network errors when communicating with console-api. These need retry logic.
ECONNREFUSED (original)
Sometimes console-web receives Error: connect ECONNREFUSED 10.43.244.214:3000 (code: ECONNREFUSED) when talking to console-api. This happens on /api/proxy/... requests and on getProfile requests (when user profile is retrieved from console-api).
Cloudflare 524 timeout (from #2466)
Cloudflare responds with 524 status code when talking to console-api on the same /api/proxy/... path (caught in Sentry).
Proposed Fix
Add retry logic when communicating from console-web to console-api, covering both ECONNREFUSED and timeout scenarios.
Consolidates: #2466
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating console-web request handling for the /api/proxy/... path and getProfile calls, then inspect how ECONNREFUSED and Cloudflare 524 responses are currently handled. Done means retry behavior covers both connection-refused and timeout scenarios without leaving these network errors unhandled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100