-
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
Poetry install with version 1.1.6 fails with file not found errors #4143
Comments
Posting an update to help others with this issue, as well as maintainers that may attempt to debug this issue. A member of our team has discovered a better workaround for this issue than downgrading from 1.1.6 to 1.0.10: Disabling the new poetry installer by running the following command appears to solve the CI/install flakiness issue for us:
Breadcrumb trail, see this comment: #3219 (comment) |
Hello @lucinvitae, these trimmed filenames are indeed strange and I believe I saw this earlier in another ticket (couldn't find it yet). You should try removing those folders. fin swimmer |
Hello @finswimmer, thanks for reaching out. These files are created at build time in a workspace which is deleted at the end of the build. So I don't have the ability to delete them afterwards. My guess is they are ephemeral build files created by the new poetry installer, which don't map properly to build requirements at a later stage and cause the resulting build instability. That's just a guess, however. |
@lucinvitae I think there are several root causes at play here. The As for this, I suspect it might be due to either a race condition or the resolver picking the wrong package.
As for this, I suspect this is a network issue or SSL?
Would it be possible for you to re-enable parallel builds but with the version from |
As an additional note, I would recommend that you enable virtualenv creation (even in your container). This ensures that compatible support library versions are used (eg: pip/virtualenv) etc. Additionally, I would also recommend poetry installation via |
In my case |
There's no way to tell what you had going on without more details -- but from the sound of it, it was far more likely to be #4242. This is related to a weird transient bug with the installer where some race condition is triggered. |
Closing for now due to lack of reproduction and old versions being reported. |
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. |
-vvv
option).pyproject.toml
format.Issue
Poetry install failures with
FileNotFoundError
exceptions occur for version 1.1.6 and are occasionally blocking the ability to build/deploy our internal apps. This occurs for multiple of our company's projects that install dependencies with poetry. The issue has been reproduced with poetry 1.1.6 and 1.1.5. It occurs locally outside of docker, locally in docker, and in CI using docker. It is sporadic, not affecting every build every time, and thus difficult to reproduce (requires running builds over and over in parallel). Due to the intermittent nature, this typically hits us in CI.Workaround: We are able to successfully workaround this
poetry install
flakiness by using Poetry version 1.0.10. Right now we have pinned poetry at that version and are unable to upgrade without seeing significant CI / CD instability. So, we are blocked from using poetry's latest features at scale.Example failure error:
Several similar
FileNotFoundError
tickets exist but are for thepoetry run
command instead of thepoetry install
command` and do not seem like the same issue:We were able to collect several verbose (
-vvv
) logs for example intermittent failures, which do not occur when retriggering the build. Logs:poetry-filenotfounderror-1.log
poetry-filenotfounderror-2.log
The exceptions, such as the one in the code block above, typically feature some filename that appears to be truncated (e.g.
No such file or directory: '/usr/local/lib/python3.8/site-packages/~11-0.9.0.dist-info
. Another example seen recently when running a local macOS Catalina environment:Note again, the trimmed filename (
~lick-7.1.2.dist-info
). Rerunning the command fixes the issue, similar to re-triggering the build in CI when we use poetry 1.1.6, which we don't anymore due to this flaky install issue.Any help would be really appreciated, because we use 1.1.6 locally for some test projects, and really like it otherwise! 🙏
The text was updated successfully, but these errors were encountered: