Julien Jerphanion
Julien Jerphanion
It is. There's a problem with the activation script on Windows as of micromamba 2.0. We are currently addressing the problem.
2.0.2 is being released and should fix this issue.
#234 resolved the cause of the problem. Updating `setup-micromamba` to 2.0.0 should resolve the issue.
Can you let us know if using micromamba 2.0.4 and setup-micromamba 2.0.2 fixed this problem?
I confirm that this has been resolved by micromamba 2.0.4 and setup-micromamba 2.0.2. See [the logs on my fork](https://github.com/jjerphan/TileDB-BioImaging/actions/runs/12033880847/job/33549080611) of https://github.com/pydata/sparse/pull/816.
Compilation on https://github.com/conda-forge/arcticdb-feedstock/pull/298 completes. I would recommend flushing the `*micromamba*` caches on GitHub Action.
Hi @alokwatve, thank you for this report! Could you [craft a minimal bug report](https://matthewrocklin.com/minimal-bug-reports)? This would allow ArcticDB's maintainers to resolve your problem more effectively. Thank you.
I cannot reproduce the errors which you report using `conda-forge/label/micromamba_dev/linux-64/micromamba-2.0.0{rc0-1,rc1-2}`. On my machine, installing those packages take around 1.5GiB of memory storage in the `$CONDA_PREFIX`, while using less than 1GiB...
The `repodata.json` is reparsed for each package (since `conda-forge::` is specified for everyone of them), causing major resource usage. This is a regression of micromamba 2.0.0.
From bisecting, e874e7ea71ceefa1f52bdfd8deb6bf5bb3129316 from https://github.com/mamba-org/mamba/pull/2986 is the culprit.