Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase REQUEST_TIMEOUT or make configurable #6787

Closed
Kaiser1989 opened this issue Oct 12, 2022 · 2 comments
Closed

Increase REQUEST_TIMEOUT or make configurable #6787

Kaiser1989 opened this issue Oct 12, 2022 · 2 comments
Labels
status/duplicate Duplicate issues

Comments

@Kaiser1989
Copy link

  • [x ] I have searched the issues of this repo and believe that this is not a duplicate.
  • [x ] I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

When trying to publish my python artifacts with poetry, running poetry publish we run into timeouts:

- Uploading xxx-py3-none-win_amd64.whl 0%
- Uploading xxx-py3-none-win_amd64.whl 100%
HTTPSConnectionPool(host='artifacts.pp-intern.tools', port=443): Read timed out. (read timeout=15)

Tried to configure it. After some investigation I found the cause for this. Poetry uses library requests and there is a hardcoded 15s timeout in constants.py: https://github.com/python-poetry/poetry/blob/master/src/poetry/utils/constants.py

Solution:
Either increase this value (e.g. 60s), or make it configureable, maybe by an env:var or by some config value.

@Kaiser1989 Kaiser1989 added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Oct 12, 2022
@neersighted neersighted added status/duplicate Duplicate issues and removed kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Oct 12, 2022
@neersighted
Copy link
Member

Duplicate #6009.

@neersighted neersighted closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2022
Copy link

github-actions bot commented Mar 1, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status/duplicate Duplicate issues
Projects
None yet
Development

No branches or pull requests

2 participants