429 responses should carry more information
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api, documentation
Research direction
Start by reviewing the API's existing 429 response behavior and rate-limit documentation. Determine whether the expected consumption limits belong in response headers, response content, or per-API documentation; done means users can identify how they exceeded the limit and find the applicable limits.
Written by the indexing model from the issue text.
Description
Very hard to determine how you overloaded the server when you get a 429.
My suggestion is that the content or headers of the response should carry the expected rate of consumption for that API. At least add the limits to the documentation for each API.
- Dominant language
- TypeScript
- Stars
- 600
- Forks
- 174
- Avg merge
- 1h 38m
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from lichess-org/api
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
lichess-org/api#637 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
lichess-org/api#660 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lichess-org/api#657 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
lichess-org/api#654 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lichess-org/api#628 ·
Similar issues
-
area:editor bug issue-form:bug P0 platform:windows review: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
1lck/Lithe-IDEA#1388 ·
Maintainers usually reply within 1 day
-
fix(api): isToolAuditEnabled swallows database read errors on auditToolOperations without loggingOpenarea: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
snapotter-hq/SnapOtter#3238 ·
Maintainers usually reply within 1 day
-
rig up --plan times out after 5 s and reports an UNKNOWN outcome while the daemon completes the planOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5216 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day