Julien Jerphanion
Julien Jerphanion
Can you let us know if you still have the issue with `2.0.6.rc0` which can be installed with: ``` mamba create -n repro "conda-forge/label/micromamba_prerelease::micromamba==2.0.6.rc0" --channel-priority=flexible ``` ? I cannot reproduce...
Do you need help with debugging?
If performance and (not just) memory alignment are of interest, we could try and mention using [`mimalloc`](https://github.com/microsoft/mimalloc) and [its dynamic override which eases some usages](https://github.com/microsoft/mimalloc?tab=readme-ov-file#dynamic-override).
The inclusion of the Huber loss is sensible to me.
For some context, https://github.com/conda/ceps/pull/75/ formalizes sharded repodata, an improved indexing solution for `conda` channels. It has been accepted, but it needs to be implemented by forges (including conda-forge), and by...
https://github.com/conda/conda/issues/14060 is the main requirement which is being implemented by https://github.com/conda/conda-index/pull/161.
I would prioritize it, since UX-wise this is what cause latency and fatigue for users.
Yes, mamba can implement the support of the sharded repodata now without waiting for conda-lock to implement it.
I am not sure about `libsolv` being usable with the sharded repodata since `libsolv` has to load all the metadata of packages upfront AFAIK.
As of now in mamba, entire channels' `repodata.json` are loaded in `libsolv`'s DataBase, then a problem is constructed and solved as far as I remember.