v0.8.3 - Mirror race actually verified
v0.8.3 — Mirror race was lying. Now actually verified.
After v0.8.2 shipped, the question was "did you actually check all the URLs work?" — turns out no, two of three mirrors were misleading.
What was broken in v0.8.1 / v0.8.2
The mirror race tested directory index reachability, not whether the actual wheel file existed on each mirror. Tsinghua / Aliyun / USTC are PyPI mirrors — they host the regular torch (CPU only) but not the +cu121 / +cu124 builds. So a Chinese user could see "fastest mirror: tsinghua (0.05s)" — and then the real download would hit HTTP 404.
Worse: the URL picked by the race wasn't even passed to download_runtime — it just always used PyTorch official anyway. So the "race" was decorative.
之前的鏡像速度測試有兩個 bug：(1) 只測目錄索引能不能連到，沒測真正的 wheel 檔案在不在那邊。Tsinghua / Aliyun 是 PyPI 鏡像，沒有 CUDA 版本的 torch。(2) 速度賽選出的 URL 沒被實際使用。
What's fixed
- Real mirror probe:
pick_fastest_mirror()now does a partial GET on the actualtorch-X.Y.Z+cuXXX-cpYY-cpYY-win_amd64.whlfilename. A mirror only wins if it's both fast AND actually has the file. - Verified mirror list: only the 3 confirmed sources stay:
download.pytorch.org(official, redirects to R2)download-r2.pytorch.org(Cloudflare R2, the actual host)mirror.sjtu.edu.cn/pytorch-wheels/(the real China mirror that hosts CUDA wheels)
- Race result actually used:
download_runtime(torch_url=...)accepts the URL chosen by the race.
Verified all 11 wheels (cp312 / win_amd64)
| Wheel | Size | Status |
|---|---|---|
| torch cu118 | 2700 MB | 206 ✓ |
| torch cu121 | 2449 MB | 206 ✓ |
| torch cu124 | 2510 MB | 206 ✓ |
| typing_extensions | 37 KB | 206 ✓ |
| filelock | 16 KB | 206 ✓ |
| fsspec | 180 KB | 206 ✓ |
| sympy | 6.2 MB | 206 ✓ |
| mpmath | 536 KB | 206 ✓ |
| networkx | 1.7 MB | 206 ✓ |
| jinja2 | 133 KB | 206 ✓ |
| MarkupSafe | 17 KB | 206 ✓ |
Download
- vid2dataset.exe (151 MB)
v0.8.x users: click 检查更新 / Check for Updates.