-
-
Notifications
You must be signed in to change notification settings - Fork 422
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
JSONDecodeError? (no content in response) #1981
Comments
It seems to happen after the first |
I have the same issue after updating pdm from 2.5.2 to 2.7.1 |
Checking PDM's dependencies on pypi, it seems the most recent update was to CacheControl, on June 1st, 5 days ago. |
Clearing the cache with |
this is breaking all our builds on pydantic 😞, see https://github.com/pydantic/pydantic/actions/runs/5187081945. Is there an easy way to get |
Sorry, it's due to the cache change #1971 |
Due to the cache broken issue, I have yanked 2.7.1. And we will work on making the cache change more smooth in the next release. |
Thanks for the quick response @frostming 🙂 |
Fixes #1981 Signed-off-by: Frost Ming <[email protected]>
Hi, sorry to bump this again after closing the issue - I am experiencing the same problem with 2.7.0. Fortunately cleaning the cache solves the problem! Perhaps it would |
Just noticed this :( Sorry for all the trouble folks. I was going back and forth between lots of versions and had no issues with the cache breaking as long as I started from an old non-split cache (i.e, older version) -- I guess I just got lucky, or I'd cleared it by accident at some point and had a better initial state. |
Hey, I'm getting these surprising errors while trying to lock dependencies.
I thought at first it was because I had a self-hosted pypi server in extra urls, but even after I removed it, I still get these errors.
I've updated all dependencies and tried a few older ones, to no avail.
Steps to reproduce
Before that one I had this:
...which seems similar: no content in the response or something.
Environment Information
The text was updated successfully, but these errors were encountered: