akash-network / akash-network/console
console-web: handle 495 errors from Provider proxy
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
Why
Provider-proxy may return 495 error, in case there is an issue with provider certificate. There are quite a lot of errors like this recently because certificates of some providers expired
What
Need to show proper alert to the user and do not report such errors to sentry
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 in console-web by tracing how Provider proxy responses are handled, focusing on the path that receives HTTP 495 errors. Confirm that a provider-certificate failure shows a user-facing alert and is excluded from Sentry reporting; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100