kenzuya/unshackle
1
0
Fork 2
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-11-15 05:25:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(serve): add operator dashboard endpoints and per-key rate limits

Browse Source
This commit is contained in:
imSp4rky
2026-09-02 23:52:55 -06:00
parent ac8f71b969
commit 8354235d56
18 changed files with 1615 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dev/rest-api/errors.md
+9
View File
@@ -109,6 +109,15 @@ but the defaults hold for the overwhelming majority of responses.
| `CONFLICT` | 409 | The target resource is in a state that disallows the action (retrying a running job, prioritising a non-queued job, clearing cache during an active download). |
| `RATE_LIMITED` | 429 | The streaming service is rate-limiting requests. Retryable. |
!!! warning "Not every `429` is `RATE_LIMITED`"
The server has a rate limit of its own. An API key over `serve.tiers.<name>.rate_limit`
or `serve.users.<key>.rate_limit` gets a `429` from the authentication middleware, before
any handler runs, so it carries no `error_code` and is not the `RATE_LIMITED` code above.
It is the shape `{"status": 429, "message": "Rate limit exceeded."}` with a `Retry-After`
header. Read `Retry-After` and wait it out rather than retrying on a backoff of your own:
the window is fixed, so an early retry only spends the next window. See
[Authentication](authentication.md#rate-limit-rejections).
### Server errors (5xx)
| Code | Status | Meaning |