request does not consider HTTP errors to be an error
Open
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Errors, such as `429: Too Many Requests` are not considered to be an error. Arguably, it should.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name a file or test. Start by locating the request-handling entry point in the JavaScript wrapper and reproduce a 429 response from the genderize API. Done means HTTP error responses such as 429 are reported as errors rather than treated as successful requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100