potentially erroneous published archive for 2.8.0

[h-vetinari]

Hi all, I'm unsure if this is the right place to report this, but there's an issue with the file pytorch-2.8.0-cpu_mkl_py311_h98f00f5_100.conda in this release.

InvalidArchiveError("Error with archive C:\Anaconda\pkgs\pytorch-2.8.0-cpu_mkl_py311_h98f00f5_100.conda. You probably need to delete and re-download or re-create this file. Message was:\n\nfailed with erro)

Originally posted by @Zalnd in #409 (comment)

For completeness, this is win-64/pytorch-2.8.0-cpu_mkl_py311_h98f00f5_100.conda.

[h-vetinari]

I was not able to reproduce this:

> mamba create -n test python=3.11 pytorch=2.8
[...]
  Package                            Version  Build                       Channel           Size
--------------------------------------------------------------------------------------------------
  Install:
--------------------------------------------------------------------------------------------------

  + bzip2                              1.0.8  h0ad9c76_8                  conda-forge     Cached
  + [...]
  + pytorch                            2.8.0  cpu_mkl_py311_h98f00f5_100  conda-forge       30MB
[...]
>mamba activate test
>python
Python 3.11.13 | packaged by conda-forge | (main, Jun  4 2025, 14:39:58) [MSC v.1943 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>>

[mgorny]

I wish there would be an actual error in that message :-).

[mgorny]

Hmm, the archive looks fine at a first glance to me too. Perhaps it's a CDN problem of some kind?

@Zalnd, did you remove it and try downloading it again?

[rgommers]

I've had a few issues like that before where the cause was having a really old version of conda of mamba that didn't recognize some metadata, unicode characters, or the like.

[Zalnd]

@h-vetinari Thank you for reporting it accordingly and for testing it.

@mgorny Yes, I did.

@rgommers Hm... I'm using the latest conda version (25.7.0) and @h-vetinari tried to reproduce the InvalidArchiveError with mamba. Perhaps it is a conda-only issue.

That's my conda info output:

     active environment : dlhub
    active env location : C:\Anaconda\envs\dlhub
            shell level : 2
       user config file : C:\Users\me\.condarc
 populated config files : C:\Anaconda\.condarc
                          C:\Users\me\.condarc
                          C:\Anaconda\envs\dlhub\.condarc
          conda version : 25.7.0
    conda-build version : not installed
         python version : 3.13.7.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=x86_64_v3
                          __conda=25.7.0=0
                          __win=10.0.26100=0
       base environment : C:\Anaconda  (writable)
      conda av data dir : C:\Anaconda\etc\conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/win-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : C:\Anaconda\pkgs
                          C:\Users\me\.conda\pkgs
                          C:\Users\me\AppData\Local\conda\conda\pkgs
       envs directories : C:\Anaconda\envs
                          C:\Users\me\.conda\envs
                          C:\Users\me\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/25.7.0 requests/2.32.5 CPython/3.13.7 Windows/11 Windows/10.0.26100 solver/libmamba conda-libmamba-solver/25.4.0 libmambapy/2.3.2 aau/0.7.3 c/. s/. e/.
          administrator : True
             netrc file : None
           offline mode : False

[mgorny]

Could you paste the full install command you're using and its output?

[Zalnd]

Just a conda update --all.

I was having a hard time getting my terminal to print the error message without truncation.

Channels:
 - conda-forge
 - defaults
Platform: win-64
Collecting package metadata (repodata.json): done
Solving environment: done

## Package Plan ##

  environment location: C:\Anaconda\envs\dlhub


The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    pytorch-2.8.0              |cpu_mkl_py311_h98f00f5_100        28.5 MB  conda-forge
    ------------------------------------------------------------
                                           Total:        28.5 MB

The following NEW packages will be INSTALLED:

  pybind11-abi       conda-forge/noarch::pybind11-abi-4-hd8ed1ab_3

The following packages will be UPDATED:

  harfbuzz                                11.5.0-h5f2951f_0 --> 11.5.1-h5f2951f_0
  libtorch                       2.7.1-cpu_mkl_hf058426_104 --> 2.8.0-cpu_mkl_h408b1a6_100
  pytorch                  2.7.1-cpu_mkl_py311_h415f141_104 --> 2.8.0-cpu_mkl_py311_h98f00f5_100
  pytorch-cpu                    2.7.1-cpu_mkl_h8b52ce0_104 --> 2.8.0-cpu_mkl_h8b52ce0_100

The following packages will be DOWNGRADED:

  pybind11                               3.0.1-pyh7a1b43c_0 --> 2.13.6-pyhc790b64_3
  pybind11-global                        3.0.1-pyh5e4992e_0 --> 2.13.6-pyh6a1d191_3


Proceed ([y]/n)?

InvalidArchiveError("Error with archive C:\\Anaconda\\pkgs\\pytorch-2.8.0-cpu_mkl_py311_h98f00f5_100.conda.  You probably need to delete and re-download or re-create this file.  Message was:\n\nfailed with error: [Errno 2] No such file or directory: 'C:\\\\Anaconda\\\\pkgs\\\\pytorch-2.8.0-cpu_mkl_py311_h98f00f5_100\\\\info\\\\test\\\\test\\\\compiled_autograd_skips\\\\TestNestedTensorSubclassCPU.test_softmax_dim_reduce_ragged_idx_greater_than_1_same_output_shape_transpose_offset_1_requires_grad_True_components_require_grad_False_cpu_float32'")

Since the package itself is fine, the issue is likely related to Windows' maximum path length limitation. Honestly, I don't remember if I have already enabled long paths on this workstation. I will enable them and try again.

Thank you all!

[Zalnd]

Just confirmed that was maximum path length limitation. The issue can be closed.

Thank you all again.

[mgorny]

Thank you. Unfortunately, looks like these are the upstream names.

[isuruf]

We should move those test files to a separate output so that users don't have to use a short path.