-
Notifications
You must be signed in to change notification settings - Fork 246
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
2023.5.7 Causing CI/CD issues #225
Comments
Interesting. If I install into a clean virtualenv I don't have this issue at all, which suggests the wheel is intact. I wonder if something is incompatible with pdm. Can you try a clean environment with pdm and one with pip to confirm whether they're behaving differently? |
Not sure if this is related, but: I'm having problems with
Downgrading to the previous |
Hi, I'm absolutely not sure that this is related, but I'm facing the "same" end-user message Here are the exact steps I'm using in my pipelines using
They were working until very recently. While executing the last command, I see a message such as
even if I already had After that, the Here are the full trace on a RedHat 8 based system: trace.txt Hope this may help |
Hey, I am having the same issue using PDM. |
@natali-avr I have a theory about what could be causing this but I think everyone is running on some remote CI system without the ability to replicate what's happening locally. I believe the issue at the core of @AndyMoreland and @riton's problems is that there is a global/system-level upgrade of |
Hi all. I ran into a similar issue, and managed to fix it, hope this might help others. I want to install some project that uses pdm, and
I am on RHEL 8, using virtualenv, created with 'python3.9 -m venv'. It turned out that the project had pdf.lock saying:
But with
So when I ran
One might claim that pdm should have done this by itself, instead of removing. I don't know pdm at all, so not opening there an issue (yet?). |
Just popping in to say that the root cause in this case was that PDM was being used to provision the environment it was itself installed in. The project in question had a dependency on an older version of Not sure it helps with the original question, but in this case at least you can avoid the issue by one of:
|
Good morning! I'm not sure if this is a PDM, requests, or certifi issue, but as of the latest release (~17 minutes ago now) I'm seeing my CI/CD builds which run
fail with this error:
Some relevant packages that are installed --
The timing for the start of these failures is to-the-minute with the latest release.
The text was updated successfully, but these errors were encountered: