microsoft / microsoft/azure-devops-python-api
Creating codeWiki Caused by ResponseError('too many 500
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
Im getting this error
raise RetryError(e, request=request)
msrest.exceptions.ClientRequestError: Error occurred in request., RetryError: HTTPSConnectionPool(host='test-web.visualstudio.com', port=443): Max retries exceeded with url: /Sample2.0/_apis/wiki/wikis (Caused by ResponseError('too many 500 error responses'))
Its able to pull the Project ids but when creating a wiki and wiki pages as codeWiki I get that error above. My PAT is in full access. here is the last part of the code
for item in wikis:
print(item.id)
wiki_client.create_wiki({"name": WIKI_NAME, "ProjectId": PROJECT_ID}, project=PROJECT_NAME)
#wiki_client.create_or_update_page(parameters={"content": "TEST_PY_PY", "id": 1}, project=PROJECT_ID, wiki_identifier=WIKI_NAME, path="/PageTest", version=None)
obj = wiki_client.create_or_update_page(parameters={"content": "TEST_PY_PY", "id": 1}, project=PROJECT_ID, wiki_identifier=WIKI_NAME, path="/PageTest", version=None)
print(obj.text)
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 wiki_client.create_wiki call and the following create_or_update_page call in the issue snippet, then reproduce the request against the Azure DevOps wiki API using the shown project and wiki values. Done means wiki creation no longer returns the reported 500-response retry error and the subsequent page operation can proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100