Honor "request moderation" responses
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Read the linked Moderating Client Request Traffic documentation first, then trace the library's request-handling entry point for CMR calls. Done means 429 responses with a Retry-After header are honored according to that documentation, with tests covering the behavior.
Written by the indexing model from the issue text.
Description
Honor the 429 responses with 'retry-after' headers, as described in Moderating Client Request Traffic
- Dominant language
- Python
- Stars
- 29
- Forks
- 32
- Avg merge
- 19h 6m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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 nasa/python_cmr
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nasa/python_cmr#108 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
nasa/python_cmr#104 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
nasa/python_cmr#94 ·
-
chore
Difficulty 3/5 1-2 days Newbie friendliness 45/100
nasa/python_cmr#93 ·
-
enhancement
nasa/python_cmr#92 · 1 assignee ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·