You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just got a conda ChecksumMismatchError and thought I should report it (I've never seen this in all my times installing torchvision envs).
I downloaded and checked the checksums of all the builds on conda (using the JSON output from conda search --json -i torchvision -c pytorch -c nvidia) and found it only affects 3 builds, all of which are torchvision 0.10.0 and Python 3.9:
So this can be safely considered a PyTorch 0.10.0 and Python 3.9 specific problem.
Hope this was not too much irrelevant info I just wanted to be sure it wasn't a broader issue since it effectively causes an outage (the package installation aborts)
The text was updated successfully, but these errors were encountered:
lmmx
changed the title
Python 3.9 build checksums are incorrect for v0.10.0
Python 3.9 conda build checksums are incorrect for v0.10.0
Aug 9, 2021
I've gone ahead and deleted the old packages and the hash mismatch appears to have been resolved, feel free to re-open the issue if still persists, see pytorch/pytorch#63006 (comment)
🐛 Bug
I just got a conda
ChecksumMismatchError
and thought I should report it (I've never seen this in all my times installing torchvision envs).I downloaded and checked the checksums of all the builds on conda (using the JSON output from
conda search --json -i torchvision -c pytorch -c nvidia
) and found it only affects 3 builds, all of which are torchvision 0.10.0 and Python 3.9:py39_cpu
py39_cu102
py39_cu111
To Reproduce
⇣
conda install -y pytorch torchvision -c pytorch # get Python 3.9
⇣
Expected behavior
The checksum should not be mismatched.
I can also reproduce manually:
⇣
⇣
Eventually re-ran it on every build and re-ran that with more info:
Essentially ran this:
This takes an awfully long time though, so I rewrote it as async (but I'll leave it in this gist rather than paste the entire thing here)
⇣
So this can be safely considered a PyTorch 0.10.0 and Python 3.9 specific problem.
Hope this was not too much irrelevant info I just wanted to be sure it wasn't a broader issue since it effectively causes an outage (the package installation aborts)
The text was updated successfully, but these errors were encountered: