Installing vllm nightly from S3 path fails but leaves uv.lock in a unparseable, bad state #15647
Description
Summary
Running twice uv sync --active leads to:
error: Failed to parse `uv.lock`
Caused by: The entry for package `vllm` v0.10.1rc2.dev397+g038e9be4e has wheel `vllm-1.0.0.dev0-cp38-abi3-manylinux1_x86_64.whl` with inconsistent version: v1.0.0.dev0
Even if uv sync --active installation fails because of vllm not following filename<>metadata consistency, I think it should not leave uv.lock in unparseable state
My OP is here:
# pyproject.toml - a single file in curdir
[build-system]
requires = ["setuptools>=65", "wheel"]
build-backend = "setuptools.build_meta"
[project]
name = "test_vllm"
version = "0.0.0.1"
requires-python = ">=3.12"
dependencies = [
"vllm",
"torch>=2.8",
"flash-attn==2.8.2",
]
[tool.uv.sources]
vllm = { url = "https://vllm-wheels.s3.amazonaws.com/038e9be4eb7a63189c8980845d80cb96957b9919/vllm-1.0.0.dev-cp38-abi3-manylinux1_x86_64.whl" }
[tool.uv]
override-dependencies = ["outlines-core==0.2.10"]Related:
- uv pip install failes for wheel URLs with placeholder #8082
- [Bug]: 1.0.0.dev placeholder doesn't work with
uv pip installvllm-project/vllm#9244
Platform
Ubuntu-22.04
Version
uv 0.8.13
Python version
Python 3.12.11