-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Running poetry install fails sometimes with new-installer #3336
Comments
The error message contains If this file is still on your local file system, would you mind trying to inspect it manually? For example verify the checksum, or since it should be just a simple zip file in disguise, try to open this archive with your usual favorite unzip program. Or maybe something like:
|
Added a step to the CI to upload the artifacts on failure and that worked for getting a copy on another failed run. Failure this time was on The sha256 from PyPi is The sha256 of the file from the artifacts on that build matches PyPi:
|
I see. I do not know how to go on on from there then. My first impression is that it could have been a similar issue as this one (probably a download went wrong), but your issue seems to be different. |
To test that it works consistently with the parallel installer disabled, I disabled it in |
We are also getting a lot of flakiness using the new installer in our CI builds. For example, those are errors from the three consecutive retries of the same build:
|
I encounter the same issue, when running in CI. It's sporadic and seems to be related to the new installer. |
We've encountered this also running our builds on gitlab-ci, randomly builds will fail, not only running directly on the runner docker executor, also inside kaniko builds. The only solution has been to disable the new installer as documented above:
|
------------ The Problems ------------ There are namely two problems which are being fixed in this issue: 1. `pyproject.toml` defines `modmail` package to be included, thus poetry searches for it but finds it be to be empty as originally we copied the poetry meta files only before installing and then copied rest of the package. 2. We are using pip to install poetry, we uses the new installer, the new installer has a known bug see python-poetry/poetry#3336 but the issue hasn't shown any acitivty since it has been opened unfortunately. ------------ The Solution ----------- 1. I have moved `COPY . .` to be ran before poetry install so poetry can find what the package to be included. 2. The only possible solution to this is to disable the old installer which was causing this bug for some reason.
------------ The Problems ------------ There are namely two problems which are being fixed in this issue: 1. `pyproject.toml` defines `modmail` package to be included, thus poetry searches for it but finds it be to be empty as originally we copied the poetry meta files only before installing and then copied rest of the package. 2. We are using pip to install poetry, we uses the new installer, the new installer has a known bug see python-poetry/poetry#3336 but the issue hasn't shown any acitivty since it has been opened unfortunately. ------------ The Solution ----------- 1. I have moved `COPY . .` to be ran before poetry install so poetry can find what the package to be included. 2. The only possible solution to this is to disable the old installer which was causing this bug for some reason.
I am seeing this issue using Poetry
error installing
|
I've also implemented the workaround in my base images and my issues with |
is this still valid? |
Yes, no new version was released to address this problem. In some repos: |
can we make the experimental not the default this has been driving me nuts for days thanks |
See #3010 (comment) for a bit more context on the Poetry Also, you might have better results if you stop doing |
Can someone confirm that this is resolved with Poetry from poetry@master (or latest pre-release). Alternatively, in environments where this is a risk, you cna also consider the mitigation. poetry config installer.max-workers=1 |
Anecdotally, I have never seen this error in Poetry 1.2.0b1 in the several weeks that my team at work has been using 1.2.0b1 both locally and in CI for multiple repos. |
Not sure why this was re-opened, but I am closing it as there have been no consistent reproductions on 1.2.0 -- please open a new issue if you are able to reproduce installer issues with 1.2.0. |
I believe the commented out code was related to this: python-poetry/poetry#3336 (comment) The code has been in commented out state for a long time and poetry 1.5.0 does no longer even support the option, so better clean up this old junk.
I believe the commented out code was related to this: python-poetry/poetry#3336 (comment) The code has been in commented out state for a long time and poetry 1.5.0 does no longer even support the option, so better clean up this old junk.
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. |
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: Ubuntu 18.04.5 and Alpine 3.12
Poetry version: 1.1.4
Link of a Gist with the contents of your pyproject.toml file: https://github.com/austinbutler/poetry-test/runs/1366900719?check_suite_focus=true#step:5:289
Issue
At random,
poetry install
will fail with the following error. The package being installed by pip changes, but thebrotli
error doesn't change.So far it doesn't seem to happen from a normal interactive shell on macOS, but that could just be random luck. However CI at work in Jenkins has been flaky and even local builds in Docker show the same issue.
What seems to fix it is setting
new-installer = false
.I realize there are already a few issues opened that are possibly similar (related to race conditions and parallel installs), but I was able to replicate it in an example GitHub action so figured maybe that could help.
The text was updated successfully, but these errors were encountered: