Frequent curl timeouts on install.python-poetry.org from GHA #10531
Replies: 1 comment
|
That connection-timeout log alone doesn't establish server load or rate limiting. However, you can remove the installer endpoint from the CI installation path while keeping Poetry pinned to 1.8.5. Poetry's CI installation recommendations support installing with pip into a separate virtual environment. On an Ubuntu runner, after your Python setup step: - name: Install pinned Poetry
shell: bash
run: |
python -m venv "$RUNNER_TEMP/poetry-cli"
"$RUNNER_TEMP/poetry-cli/bin/python" -m pip install "poetry==1.8.5"
echo "$RUNNER_TEMP/poetry-cli/bin" >> "$GITHUB_PATH"
- name: Check Poetry
run: poetry --versionThis still needs access to your package index, but doesn't contact install.python-poetry.org. Keep that tool environment separate from the project's environment, and don't activate it when running Poetry to manage the project. Retaining your existing compatible Python version also avoids turning this into a Poetry upgrade. GitHub applies GITHUB_PATH additions to subsequent steps, hence the separate version-check step. This is a documented alternative installation path, rather than a diagnosis of the historical outage. |
Uh oh!
There was an error while loading. Please reload this page.
Starting in the last couple of weeks, we've started having intermittent but frequent failures in our GitHub Actions that involve installing Poetry, along the lines of:
Is the server having load issues, or is there some sort of rate-limiting added recently that may be affecting GitHub Actions runners specifically?
All reactions