APOD API no longer working!
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 555
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 3
Description
The APOD API only responds when you send the WRONG API key! When a valid key, or the Demo key is used, it doesn't reply at all ( a timeout is thrown).
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
No file, test, or endpoint is named. Start by reproducing the APOD API request with a valid key, the Demo key, and an invalid key, then compare the responses and timeout behavior. Done means valid and Demo keys receive a response without timing out, with the behavior verified against the reported case.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100