vllm - ✅(Solved) Fix [CI/Build] pre-commit pip-compile fails for ~half of recent PRs: PyPI quarantined the `lightning` project [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#41376Fetched 2026-05-01 05:33:53
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
closed ×1cross-referenced ×1referenced ×1renamed ×1

PyPI has flagged the lightning project as quarantined. The simple index returns <meta name="pypi:project-status" content="quarantined"> with zero release files exposed:

$ curl -s https://pypi.org/simple/lightning/ | head
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta name="pypi:repository-version" content="1.4">
<meta name="pypi:project-status" content="quarantined">    <title>Links for lightning</title>
  </head>
  <body>
    <h1>Links for lightning</h1>
</body>
</html>

Every published terratorch version transitively requires lightning, and torchgeo==0.7.0 (in requirements/test/rocm.in) requires lightning[pytorch-extra]. As a result the pip-compile and pip-compile-rocm pre-commit hooks abort with × No solution found ... Because there are no versions of lightning .... Pre-releases do not help (the quarantine hides everything).

Root Cause

Every published terratorch version transitively requires lightning, and torchgeo==0.7.0 (in requirements/test/rocm.in) requires lightning[pytorch-extra]. As a result the pip-compile and pip-compile-rocm pre-commit hooks abort with × No solution found ... Because there are no versions of lightning .... Pre-releases do not help (the quarantine hides everything).

Fix Action

Fix

Comment out terratorch in requirements/test/cuda.in and requirements/test/rocm.in, plus torchgeo==0.7.0 in rocm.in (it transitively pulls lightning[pytorch-extra]). PR at #41377. The Prithvi tests get skipped temporarily; revert once PyPI lifts the quarantine.

PR fix notes

PR #41377: [CI/Build] Skip terratorch + torchgeo while PyPI has lightning quarantined

Description (problem / solution / changelog)

Fixes #41376.

PyPI is currently serving the lightning project as quarantined: the simple index has <meta name="pypi:project-status" content="quarantined"> with zero release files exposed. Every published terratorch version transitively requires lightning, and torchgeo==0.7.0 (in requirements/test/rocm.in) requires lightning[pytorch-extra], so the pip-compile and pip-compile-rocm pre-commit hooks abort with:

× No solution found when resolving dependencies:
  ╰─▶ Because there are no versions of lightning and terratorch>=1.2.2 depends
      on lightning>=2.6.0, we can conclude that terratorch>=1.2.2 cannot be used.

--prerelease=allow does not help — the quarantine hides every version, including pre-releases.

This commit comments out terratorch in requirements/test/cuda.in + requirements/test/rocm.in, plus torchgeo==0.7.0 in rocm.in, and regenerates both lock files. Each comment block points at #41376 so the revert is mechanical once PyPI lifts the quarantine.

The Prithvi tests are skipped while this is in place. Production code that ships terratorch integration (vllm/model_executor/models/terratorch.py, vllm/renderers/registry.py) is unaffected — those are runtime-optional imports installed by users who actually want Prithvi.

Test plan

pre-commit run pip-compile      --files requirements/test/cuda.in
pre-commit run pip-compile-rocm --files requirements/test/rocm.in
pre-commit run pip-compile-xpu  --files requirements/test/xpu.in

Test result

All three hooks pass on the resulting tree:

pip-compile..............................................................Passed
pip-compile-rocm.........................................................Passed
pip-compile-xpu..........................................................Passed

grep -c "terratorch\|torchgeo" requirements/test/cuda.txt requirements/test/rocm.txt0 / 0 (cleanly removed from both lockfiles).

AI assistance was used in drafting this PR.


<details> <summary>Essential Elements of an Effective PR Description Checklist</summary>
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results.
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
</details>

Changed files

  • requirements/test/cuda.in (modified, +5/-1)
  • requirements/test/cuda.txt (modified, +11/-274)
  • requirements/test/rocm.in (modified, +8/-2)
  • requirements/test/rocm.txt (modified, +13/-265)
  • tests/entrypoints/openai/chat_completion/test_vision_embeds.py (modified, +11/-0)
  • tests/models/multimodal/pooling/test_prithvi_mae.py (modified, +5/-0)
  • tests/models/test_terratorch.py (modified, +5/-0)
  • tests/plugins_tests/test_terratorch_io_processor_plugins.py (modified, +5/-0)

Code Example

$ curl -s https://pypi.org/simple/lightning/ | head
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta name="pypi:repository-version" content="1.4">
<meta name="pypi:project-status" content="quarantined">    <title>Links for lightning</title>
  </head>
  <body>
    <h1>Links for lightning</h1>
</body>
</html>

---

$ echo 'terratorch>=1.2.2' > probe.in
$ uv pip compile probe.in -o probe.txt
× No solution found when resolving dependencies:
  ╰─▶ Because there are no versions of lightning and terratorch>=1.2.2 depends
      on lightning>=2.6.0, we can conclude that terratorch>=1.2.2 cannot be used.
RAW_BUFFERClick to expand / collapse

Summary

PyPI has flagged the lightning project as quarantined. The simple index returns <meta name="pypi:project-status" content="quarantined"> with zero release files exposed:

$ curl -s https://pypi.org/simple/lightning/ | head
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta name="pypi:repository-version" content="1.4">
<meta name="pypi:project-status" content="quarantined">    <title>Links for lightning</title>
  </head>
  <body>
    <h1>Links for lightning</h1>
</body>
</html>

Every published terratorch version transitively requires lightning, and torchgeo==0.7.0 (in requirements/test/rocm.in) requires lightning[pytorch-extra]. As a result the pip-compile and pip-compile-rocm pre-commit hooks abort with × No solution found ... Because there are no versions of lightning .... Pre-releases do not help (the quarantine hides everything).

Affected

pre-commit is failing on every PR that triggers re-resolution. Sampled 12 recent open PRs touched today: 6 fail, 2 pass (stale, ran before the quarantine), 3 skipped, 1 too new. Examples of failing PRs: #40808, #41255, #41318, #41366. Main commit ff449b6426 shows pre-commit: success but only because that status was recorded before the quarantine; re-running pre-commit on main HEAD now reproduces the failure.

Root cause confirmation

Reproduces locally with uv 0.9.26:

$ echo 'terratorch>=1.2.2' > probe.in
$ uv pip compile probe.in -o probe.txt
× No solution found when resolving dependencies:
  ╰─▶ Because there are no versions of lightning and terratorch>=1.2.2 depends
      on lightning>=2.6.0, we can conclude that terratorch>=1.2.2 cannot be used.

Same with --prerelease=allow. Removing terratorch resolves cleanly.

Fix

Comment out terratorch in requirements/test/cuda.in and requirements/test/rocm.in, plus torchgeo==0.7.0 in rocm.in (it transitively pulls lightning[pytorch-extra]). PR at #41377. The Prithvi tests get skipped temporarily; revert once PyPI lifts the quarantine.

extent analysis

TL;DR

Comment out dependencies that transitively require the quarantined lightning project to resolve the pip-compile and pip-compile-rocm pre-commit hook failures.

Guidance

  • Identify and comment out dependencies that require lightning, such as terratorch and torchgeo==0.7.0, in the affected requirements files.
  • Verify that the pre-commit hooks pass after commenting out these dependencies.
  • Temporarily skip tests that rely on the commented-out dependencies, such as the Prithvi tests.
  • Monitor the PyPI status of the lightning project and revert the changes once the quarantine is lifted.

Notes

This workaround assumes that the lightning project will be reinstated on PyPI. If the project is permanently removed, alternative dependencies may need to be found.

Recommendation

Apply the workaround by commenting out the affected dependencies, as it allows the pre-commit hooks to pass and the project to continue functioning, albeit with temporary test skips.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - ✅(Solved) Fix [CI/Build] pre-commit pip-compile fails for ~half of recent PRs: PyPI quarantined the `lightning` project [1 pull requests, 1 participants]