microsoft / microsoft/azure-devops-python-api
rate-limiting support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
Azure Devops includes rate limits that could be complex to predict in an automated solution. According to the documentation, the endpoints provide headers in responses in the instances that the client has hit a rate limiting threshold.
Is responding to the Retry-After header as discussed as recommendations in the API on the roadmap?
The API uses msrest as an HTTP library, which doesn't appear to support it at this time. Note, much of the Azure SDK uses azure-core which provides Retry-After support.
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.
Research direction
Start with the Azure DevOps rate-limit and Retry-After documentation linked in the issue, then inspect how the client uses msrest and compare the Retry-After support in azure-core. Clarify whether the intended scope is client-wide support and define the expected behavior before implementation; done should include an agreed scope and coverage for the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100