-
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
Upgrading packages from private repositories fails using cert and client-cert #3483
Comments
Yes, it's because the certs aren't provided to the second request which actually downloads the archive. I'm posting a pull-request to fix this this morning. |
Additional context: The See lib/poetry/installation/executor.py:616:
Without it, I get errors like this:
|
+1 for me, experiencing Unknown CA in packet data followed by client FIN. This is in regards specifically to
|
With the addition of a patch I supplied in the PR 3490's comments, this seems to fix the issue that we're experiencing when attempting to download an archive from a private pypi repo that requires client certs for all accesses. |
Also seeing this issue, cant post anymore info but we are able to pull from private repo using certs and using |
Any updates on this? Currently blocking our project from upgrading poetry past 1.0.10 |
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
To configure the cert and client-cert I am using:
... from the custom CA & TLS instructions.
And from pyproject.toml:
When doing a
poetry update
to get the latest packages, it fails to get packages from private repositories.It fails with:
... I started to debug that error it looked like the cert and CA were simply not provided in the http request. Actually here's what I saw:
A single successful request where the cert and CA were passed:
And then 5 failed retries that had the SSLCertVerificationError:
And in those 5 requests it looked like the cert and CA were not provided. So in my CI build I am not able to install
<package>
which happens to be an upgrade. I believe this started to happen with 1.1.0 as I can force version 1.0.10 and then the CI build will succeed and the package will install successfully.The text was updated successfully, but these errors were encountered: