8000 [false positive]: channeldata not downloadable (missing `repodata.json.zst`?) · Issue #1175 · conda/infrastructure · GitHub 8000
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[false positive]: channeldata not downloadable (missing repodata.json.zst?) #1175
Closed
@h-vetinari

Description

@h-vetinari

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

Running mamba create -n test python=3.12 fails when trying to download channel metadata

conda-forge/linux-64 ━━━━━━━━━━━╸━━━━━━━━━━━━━━━╸━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   0.0 B /  ??.?MB @  ??.?MB/s  6.1s
conda-forge/noarch   ━━━━━━━━━━━━━━━╸━━━━━━━━━━━━━━━╸━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   0.0 B /  ??.?MB @  ??.?MB/s  6.1swarning  libmamba Download error (7) Could not connect to server [https://conda.anaconda.org/conda-forge/linux-64/repodata.json.zst]
    Failed to connect to conda.anaconda.org port 443 after 6288 ms: Could not connect to server
warning  libmamba Retrying in 2 seconds
warning  libmamba Download error (7) Could not connect to server [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst]
[+] 12.5s

This happens a few times and is then ends in

critical libmamba Multiple errors occurred:
    Download error (7) Could not connect to server [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst]
    Failed to connect to conda.anaconda.org port 443 after 6261 ms: Could not connect to server
    Subdir conda-forge/noarch not loaded!
    If you run into this error repeatedly, your package cache may be corrupted.
    Please try running `mamba clean -a` to remove this cache before retrying the operation.

Double-checking if the same issue exists with curl, I see

curl -L https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst | sha256sum
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0
curl: (7) Failed to connect to conda.anaconda.org port 443 after 6287 ms: Couldn't connect to server
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  -

Looking at https://conda.anaconda.org/conda-forge/noarch/, I see that the channel is online, and while repodata.json and repodata.json.bz2 exist, the .zst variant doesn't.

Is this the rollout of a new feature and there's some temporarily inconsistent metadata? 🤔

Triple-checking with create -n test python=3.12, I see the same

Collecting package metadata (repodata.json): | Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f95fe8cb9e0>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /t/<TOKEN>/conda-forge/noarch/repodata.json.zst

[...]

failed

CondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://conda.anaconda.org/conda-forge/linux-64/repodata.json>
Elapsed: -

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
'https//conda.anaconda.org/conda-forge/linux-64'

This has been happening for the last 20min consistently, so it doesn't seem to be either flaky or completely transitory. My internet works fine for everything else.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    type::bugdescribes erroneous operation, use severity::* to classify the type

    Type

    No type

    Projects

    Status

    🏁 Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0