Retry on `M_LIMIT_EXCEEDED`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with HTTPAPI's existing retry handling and the MLimitExceeded path; inspect how retry_after_ms is read from the response and how backoff/retry_count are applied. Done means M_LIMIT_EXCEEDED waits for the specified delay when present and otherwise follows the existing fallback retry behavior, with coverage for both cases.
Written by the indexing model from the issue text.
Description
It seems currently the HTTPAPI may retry after waiting a while on some network and client errors, but raises MLimitExceeded errors.
I would like to have the API wait for the retry_after_ms time specified in the response, and fall back to the backoff/retry_count method if it is missing.
- Dominant language
- Python
- Stars
- 249
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
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.
More from mautrix/python
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100