CDN sync down for Bioconda

[dpryan79]

I posted a new repodata patches package a number of hours ago but it's still not showing up with conda search bioconda-repodata-patches. This is the package that modifies our repodata, so it should also result in all of the nanoqc package requiring bokeh >=2.4,<3 rather than just bokeh with no version restrictions.

[barabo]

This is the content of the repodata patches being used by the CDN cloning process.

(base) canderson@Carls-MacBook-Pro-2 Downloads % tar -xvjpf bioconda-repodata-patches-20230228-hdfd78af_0.tar.bz2
x info/hash_input.json
x info/recipe/build.sh
x info/link.json
x info/files
x info/recipe/README
x info/test/run_test.sh
x info/test/run_test.bat
x info/index.json
x info/recipe/meta.yaml.template
x info/paths.json
x info/recipe/meta.yaml
x info/recipe/show_diff.py
x info/recipe/conda_build_config.yaml
x info/about.json
x info/recipe/gen_patch_json.py
x info/git
x osx-64/patch_instructions.json
x linux-64/patch_instructions.json
x noarch/patch_instructions.json

@dpryan79 - Just to confirm, are you using linux-64 or osx-64 or noarch?

[barabo]

Also, this is what I see in the tarball:

(base) canderson@Carls-MacBook-Pro-2 Downloads % grep bokeh */patch_instructions.json
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
linux-64/patch_instructions.json:        "bokeh >=2.4,<3",
noarch/patch_instructions.json:        "bokeh >=2.4,<3",
noarch/patch_instructions.json:        "bokeh >=2.4,<3",
noarch/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",
osx-64/patch_instructions.json:        "bokeh >=2.4,<3",

[barabo]

Can you confirm that this is the correct repodata patches tarball?

[barabo]

This is what I see for the most recent bioconda patches, too.

(base) canderson@Carls-MacBook-Pro-2 Downloads % conda search -c bioconda bioconda-repodata-patches | tail
bioconda-repodata-patches        20220206 py310hdfd78af_0  bioconda
bioconda-repodata-patches        20220803         py310_0  bioconda
bioconda-repodata-patches        20220803 py310hdfd78af_0  bioconda
bioconda-repodata-patches        20220921               0  bioconda
bioconda-repodata-patches        20220921               1  bioconda
bioconda-repodata-patches        20220921      hdfd78af_0  bioconda
bioconda-repodata-patches        20220921      hdfd78af_1  bioconda
bioconda-repodata-patches        20221115               0  bioconda
bioconda-repodata-patches        20221115      hdfd78af_0  bioconda
bioconda-repodata-patches        20230228      hdfd78af_0  bioconda

[dpryan79]

Weird, must indeed have been bad timing, since I see everything now.

[johanneskoester]

Trying another channel since we had no success on gitter so far: Bioconda-CDN is out of sync again.

$ curl -I -s https://conda.anaconda.org/bioconda/channeldata.json|grep modified
last-modified: Wed, 15 Mar 2023 14:35:08 GMT

[barabo]

The clone successfully finished it's regular run on 2023-03-15 at 14:30 UTC. It didn't reboot as normal and we don't have monitoring to catch non-failure instances that fail to shut down. I'm looking into adding monitoring for this, but that's what I know so far.

After rebooting the clone VM, it recovered on its own.

[johanneskoester]

Ok, thanks!