microsoft / microsoft/artifacts-keyring
Artifacts keyring ignores pip.ini proxyb setrings
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 45
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
At least when using the library with pip/vscode/azure initially artifacts-keyring ignores the pip.ini proxy settings leading to some confusing behavior, setting global proxy seems to fix the issue
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 by reproducing the behavior with pip, VS Code, and Azure Artifacts using proxy settings in pip.ini, then inspect where artifacts-keyring reads or ignores those settings. Done means the configured pip.ini proxy settings are respected without requiring a global proxy, with the behavior verified in the affected setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100