Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not read JSON repodata file parse error line 593230: subdir mismatch #780

Closed
jwarwick-delfi opened this issue Jun 8, 2023 · 4 comments
Assignees
Labels
downstream::conda-forge this issue/PR impacts the conda-forge community in-progress issue is actively being worked on severity::2 critical; broken functionality with an unacceptably complex workaround source::community catch-all for issues filed by community members type::bug describes erroneous operation, use severity::* to classify the type

Comments

@jwarwick-delfi
Copy link

jwarwick-delfi commented Jun 8, 2023

What happened?

About an hour ago, we started to get these error messages in our CI build.

RuntimeError: Could not read JSON repodata file (/opt/micromamba/pkgs/cache/47929eba.json) parse error line 593230: subdir mismatch

It appears that we're not the only ones with that issue - I found it in the build logs in the coda-forge admin-migrations project.
https://github.com/conda-forge/admin-migrations/actions/runs/5215250509/jobs/9412559109#step:4:644

Conda Details

conda info
environment variables:
                 CIO_TEST=<not set>
  CONDA_AUTO_UPDATE_CONDA=false
        CONDA_DEFAULT_ENV=base
             CONDA_PREFIX=/opt/micromamba
    CONDA_PROMPT_MODIFIER=(base)
               CONDA_ROOT=/opt/micromamba
              CONDA_SHLVL=1
           CURL_CA_BUNDLE=<not set>
               LD_PRELOAD=<not set>
                     PATH=/opt/micromamba/bin:/opt/micromamba/condabin:/usr/local/sbin:/usr/loca
                          l/bin:/usr/sbin:/usr/bin:/sbin:/bin
       REQUESTS_CA_BUNDLE=<not set>
            SSL_CERT_FILE=<not set>

     active environment : base
    active env location : /opt/micromamba
            shell level : 1
       user config file : /root/.condarc
 populated config files : 
          conda version : 23.3.1
    conda-build version : not installed
         python version : 3.9.16.final.0
       virtual packages : __archspec=1=x86_64
                          __glibc=2.31=0
                          __linux=5.15.0=0
                          __unix=0=0
       base environment : /opt/micromamba  (writable)
      conda av data dir : /opt/micromamba/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /opt/micromamba/pkgs
                          /root/.conda/pkgs
       envs directories : /opt/micromamba/envs
                          /root/.conda/envs
               platform : linux-64
             user-agent : conda/23.3.1 requests/2.29.0 CPython/3.9.16 Linux/5.15.0-1039-azure ubuntu/20.04.6 glibc/2.31
                UID:GID : 0:0
             netrc file : None
           offline mode : False
@jwarwick-delfi jwarwick-delfi added the type::bug describes erroneous operation, use severity::* to classify the type label Jun 8, 2023
@colt18
Copy link

colt18 commented Jun 8, 2023

Same here. You guys needs to address this asap that some packages have directory mismatch. Conda-forge is unusable right now.

@kenodegard
Copy link
Contributor

we are aware of this issue

for the conda-forge specific status updates see conda-forge/status#144

@kenodegard kenodegard transferred this issue from conda/conda Jun 8, 2023
@kenodegard kenodegard added source::community catch-all for issues filed by community members downstream::conda-forge this issue/PR impacts the conda-forge community labels Jun 8, 2023
@kenodegard
Copy link
Contributor

Repodatas have been regenerated and the subdir mismatch is no longer present.

@kenodegard kenodegard added in-progress issue is actively being worked on severity::2 critical; broken functionality with an unacceptably complex workaround labels Jun 8, 2023
@kenodegard
Copy link
Contributor

closing this since the immediate issue has been resolved

conda/conda-index#105 is a potential solution to detect this issue in the future

@kenodegard kenodegard self-assigned this Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
downstream::conda-forge this issue/PR impacts the conda-forge community in-progress issue is actively being worked on severity::2 critical; broken functionality with an unacceptably complex workaround source::community catch-all for issues filed by community members type::bug describes erroneous operation, use severity::* to classify the type
Projects
Archived in project
Development

No branches or pull requests

3 participants