-
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
Can't use poetry install after upgrading to 1.2.0 #6488
Comments
Looks like a novel (Windows) version of #1917, where attempting to detect a keyring leads to unhandled errors. |
I had tons of issues with keyring on ubuntu too ... but managed to solve them by disabling keyring |
This regression also affects running Poetry on Gitlab's shared Windows runners. See e.g. good run with Poetry 1.1.14, bad run with Poetry 1.2.0. |
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).Issue
I am installing a python project using poetry on a docker image.
Until recently it was working pretty well until we started to get the following error:
(1312, 'CredRead', 'A specified logon session does not exist. It may already have been terminated.')
The python code itself did not change much, the base image for the image that I am trying to generate did not change.
When I noticed poetry was upgraded, I downgraded it to version 1.1.15 and it started to work again.
Upgrading from 1.1.15 to 1.2.0 cause the reported error to show up.
What could cause it ?
Here is the full log:
The text was updated successfully, but these errors were encountered: