Fix halide-llvm lockfile URLs pointing at old pypiserver - #9281
Merged
Conversation
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.
alexreinking
requested review from
derek-gerstmann,
mcourteaux,
shoaibkamil and
slomp
August 5, 2026 15:57
shoaibkamil
approved these changes
Aug 5, 2026
shoaibkamil
left a comment
Contributor
There was a problem hiding this comment.
Unless someone's figured out how to make malicious changes without altering sha256 hashes, this looks safe.
4 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. 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. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes
halide-llvm's three pinned lockfile entries (21.1.8,22.1.7,23.0.0.dev100667+g9bf20bdf) viauv lock --refresh-package halide-llvmso their recorded wheel URLs point athalide/pypi(GitHub Releases) instead of the retiredpypi.halide-lang.org/packages/...pypiserver path.Why -- this is not a caching issue, it's permanent
uv.lockrecords the exact wheel URL and hash per platform for each pinned version, not just a re-resolvable index reference. Now thatpypi.halide-lang.orgDNS points athalide/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 ofuv'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/pypididn't corrupt anything).Test plan
uv lock --refresh-package halide-llvmran clean, pre-commit's "ensure uv.lock is up to date" hook passes.urlfield changed per wheel;hashis byte-identical old vs. new for all 24 entries.ci-llvm-21/ci-llvm-22/ci-llvm-maindependency groups fail to install on any fresh checkout or cold CI runner.