Differentiate between API error and API being down
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 31
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Fusera/sracp should differentiate between an API error, and a 404 error.
I think a 404 error should say that API error, and suggest contacting https://www.ncbi.nlm.nih.gov/home/about/contact/
Contributor guide
No contributing guide indexed for this repository
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 tracing sracp's handling of API responses and how it currently reports API errors versus 404 responses. Confirm the intended 404 wording and contact link from the issue, then verify that the resulting message distinguishes an unavailable API from an API error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100