Zanie Blue
Zanie Blue
@sylbeth the blocker to implementing this is https://github.com/astral-sh/uv/issues/8949#issuecomment-2465998739 — note your example drops the constraints from the `project.dependencies` table which isn't desirable.
Cool. Related https://github.com/python/steering-council/issues/256
Thanks for the report!
Weird, I don't understand what's going on here. We can look into this.
I have no qualms with exposing this via an environment variable, though, since nobody else has asked for this, I would appreciate if you opened an issue with Meltano asking...
It hangs at that log line? Does using `--no-sync` make it complete immediately?
This appears to be reproducible with just `uv lock` ``` ❯ docker run -it astral/uv:bookworm bash -c "git clone https://github.com/alex-shapiro/PufferLib && cd PufferLib && git checkout 21807b34145822e307314dd0e3b503139c6aaa97 && uv lock...
Oh, uhh this is suspicious? You have a _massive_ conflict list ``` conflicts = [ [ { extra = "avalon" }, { extra = "atari" }, { extra = "box2d"...
I'm still a bit confused about where we're stuck though.
If I delete the lockfile and resolve from scratch, we hang _after_ resolution, e.g.: ``` root@33dda518e74d:/PufferLib# uv lock --dry-run Using CPython 3.13.9 Resolved 282 packages in 1.35s ``` Very peculiar.