Skip to content

Fix halide-llvm lockfile URLs pointing at old pypiserver - #9281

Merged
alexreinking merged 1 commit into
mainfrom
fix-halide-llvm-lockfile-urls
Aug 5, 2026
Merged

Fix halide-llvm lockfile URLs pointing at old pypiserver#9281
alexreinking merged 1 commit into
mainfrom
fix-halide-llvm-lockfile-urls

Conversation

@alexreinking

Copy link
Copy Markdown
Member

Summary

Refreshes halide-llvm's three pinned lockfile entries (21.1.8, 22.1.7, 23.0.0.dev100667+g9bf20bdf) via uv lock --refresh-package halide-llvm so their recorded wheel URLs point at halide/pypi (GitHub Releases) instead of the retired pypi.halide-lang.org/packages/... pypiserver path.

Why -- this is not a caching issue, it's permanent

uv.lock records the exact wheel URL and hash per platform for each pinned version, not just a re-resolvable index reference. Now that pypi.halide-lang.org DNS points at halide/pypi (GitHub Releases + Pages) instead of the old MIT-hosted pypiserver, the old /packages/<file> URLs baked into the committed lockfile 404 -- permanently, on every CI run, independent of uv's own HTTP cache (a cold runner with zero cache hits this exactly the same way).

Every hash is unchanged between old and new -- confirms this is purely a URL fix, not a content difference (i.e. the earlier migration to halide/pypi didn't corrupt anything).

Test plan

  • uv lock --refresh-package halide-llvm ran clean, pre-commit's "ensure uv.lock is up to date" hook passes.
  • Manually diffed every changed line: only the url field changed per wheel; hash is byte-identical old vs. new for all 24 entries.
  • Recommend merging this promptly -- until it lands, ci-llvm-21/ci-llvm-22/ci-llvm-main dependency groups fail to install on any fresh checkout or cold CI runner.

uv.lock hardcodes the exact wheel URL and hash per platform for every
pinned halide-llvm version, not just a resolvable index reference. Now
that pypi.halide-lang.org serves halide/pypi (GitHub Releases + Pages)
instead of the old pypiserver, the old /packages/<file> URLs baked into
this lockfile 404 permanently -- independent of any uv cache, cold
runner or not. Refreshed via 'uv lock --refresh-package halide-llvm';
every hash is unchanged, confirming no content difference, just a URL
fix.

@shoaibkamil shoaibkamil left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless someone's figured out how to make malicious changes without altering sha256 hashes, this looks safe.

@alexreinking
alexreinking merged commit 7db5e2c into main Aug 5, 2026
18 of 20 checks passed
@alexreinking
alexreinking deleted the fix-halide-llvm-lockfile-urls branch August 5, 2026 16:24
@codecov

codecov Bot commented Aug 5, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.22%. Comparing base (0dba9f1) to head (3d7915c).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9281      +/-   ##
==========================================
+ Coverage   70.14%   70.22%   +0.07%     
==========================================
  Files         257      257              
  Lines       79162    79162              
  Branches    18979    18979              
==========================================
+ Hits        55529    55589      +60     
+ Misses      17881    17874       -7     
+ Partials     5752     5699      -53     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

2 participants