Open jaimergp opened 2 years ago
Is it safe to assume that this warning is now gone after #2433? @AntoinePrv
Looks like the current behavior is that the channel is not reloaded (leading to update/install not fetching this data), and there is no warning about it. Installing new packages seems to work if there is no conflict with the existing one. Updates do not fetch more recent data from that channel leading to a potential noop.
Not sure what should be the desired behavior, probably reloading that channel, and including it in the solv data. Atlernatively we should write some message (maybe not through the log).
For context:
Let's say we have the following situation:
channels: [defaults]
mamba create -n my_env conda-forge::xz python
. As a result, most packages come fromdefaults
, butxz
comes from conda-forge.my_env
, without specifyingconda-forge
as a channel; e.g.conda install pytest
In this situation, libmamba will print a red error message to stderr:
The message is accurate, because
xz
might have an update onconda-forge
but we can't tell because the user didn't includeconda-forge
in the channel list. Interestingly, this doesn't lead to an actual error. It's more of a (too loud?) warning.We can avoid this message by making sure that the channels returned by
PrefixData
are also included in the repodata download list. See PR forconda-libmamba-solver
here as a potential implementation idea formamba
.The question is more along of the lines of: should we actually do this?
conda/conda
source does mention this in the comments, raising concerns about expired tokens or auth. If we do it, is it going to imply too much of an overhead? Is it really necessary?The other question is whether the libmamba error message below should be downgraded to a warning instead, to cause less alarming feedback from users.
https://github.com/mamba-org/mamba/blob/32e47ae7febb760be255e0d424bf1f9bb84b1e87/libmamba/src/core/solver.cpp#L117-L118
Thanks!