Skip to content

release(0.1.19): pin torch<2.11 + GPU-compat self-check#30

Merged
zhen-he merged 1 commit into
mainfrom
release/0.1.19
May 3, 2026
Merged

release(0.1.19): pin torch<2.11 + GPU-compat self-check#30
zhen-he merged 1 commit into
mainfrom
release/0.1.19

Conversation

@zhen-he

@zhen-he zhen-he commented May 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

Pin torch<2.11 so default pip install scmidas works on V100/Pascal GPUs.

torch 2.11 dropped Volta (V100, CC 7.0) and Pascal (P100/GTX 10xx, CC 6.x) from its default cu128/cu129 wheels. Without this fix, pip install scmidas would silently install a torch that fails at the first CUDA op with no kernel image is available.

Changes

  • pyproject.toml: torch<3torch<2.11 (+ matching torchvision<0.26 / torchaudio<2.11)
  • src/scmidas/__init__.py: one-time GPU self-check at import — translates the cryptic CUDA error into actionable guidance (downgrade torch or use cu126 wheel) for users who manually upgrade past the cap
  • .github/workflows/test.yml: replace the experimental torch latest job with a blocking torch 2.10 job (the new upper bound)
  • pyproject.toml: bump to 0.1.19
  • docs/source/release.md: 0.1.19 entry

Test plan

  • pytest tests/ — 37/37 passing locally on torch 2.8
  • CI matrix green (torch 2.5 × py3.10/3.11/3.12, torch 2.8 × py3.12, torch 2.10 × py3.12)

torch 2.11 dropped Volta (V100, CC 7.0) and Pascal (P100/GTX 10xx,
CC 6.x) from its default cu128/cu129 wheels. With the previous <3
upper bound, `pip install scmidas` on those GPUs would silently install
a broken torch — the first CUDA op would raise "no kernel image is
available" from somewhere deep in the user's training loop.

This patch:
* tightens the upper bound to torch<2.11 (matching torchvision<0.26
  and torchaudio<2.11) so default installs work on Volta/Pascal too;
* adds a one-time GPU self-check at import that translates the cryptic
  CUDA error into actionable advice (downgrade torch or use cu126);
* expands the CI matrix to test the new upper bound (torch 2.10 in
  place of the previous experimental "torch latest" job).
@zhen-he zhen-he merged commit 2f8b024 into main May 3, 2026
5 checks passed
@zhen-he zhen-he deleted the release/0.1.19 branch May 3, 2026 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant