Zachary Vorhies
Zachary Vorhies
Just had it happen again Attached is a full archive of the FastLED repo when it happens ``` Zach Vorhies@DESKTOP-I3718DO MINGW64 ~/dev/fastled (master) $ ./install Using CPython 3.11.5 Creating virtual...
It's about a 1gb so far to large for github. However, I've put this on a private server for you to download. I'll keep it open for 24 hours: https://5a97-98-97-26-124.ngrok-free.app
It also just resolved itself, so the 5 min limit on a the pypi cache seems like it's a good bet that this is what is happening.
I know that pypi does NOT reflect versions immediately available. I just saw this same error propagate through our test chain, we test lots of devices for FastLED. So what...
Yeah, just hit this again while doing `uv sync` Now I have to wait for some timeout to happen. Output: ```bash Zach Vorhies@DESKTOP-I3718DO MINGW64 ~/dev/fastled-wasm (main) $ uv sync ×...
I can even uv pip install it, but uv sync then fails. ```bash Zach Vorhies@DESKTOP-I3718DO MINGW64 ~/dev/fastled-wasm (main) $ uv pip install static-npm==1.0.5 Audited 1 package in 98ms Zach Vorhies@DESKTOP-I3718DO...
Oh I see, other's are reporting the problem too: https://github.com/astral-sh/uv/issues/2538 Can you just make uv sync break through the cache on initial failure?
If there is a re-distributable can it please be patched for win10 users? I'm hitting this too.
The only way to work around this is to invoke exit on the command line