conda install/remove <package> throws 304/404 error failing on (probably) response/JSON basis about conda-libmamba-solver HOT 9 CLOSED

Thanks for the report!

The libmamba solver relies on libmamba's internal repodata fetching routines, so if it's not supported by that library, we might error out badly. We saw this already with s3:// channels, but I guess there are more cases out there.

I am thinking we might need to provide a fallback mechanism to rely on conda's repodata fetching mechanism if libmamba's failed. It might be cause some overhead, but it should work. One challenge will be how to test things for settings like yours (on-prem stuff), but we'll get there.

I'll keep you posted!

from conda-libmamba-solver.

from conda-libmamba-solver.

On a second look, I do see that the log file mentions the solver doing its work. That means the repodata was successfully loaded by libmamba and a solution was indeed calculated! I think what's going on has to do with the "check for updates" conda code that runs after the solver has done its work, but before the transaction object is generated so the packages are downloaded / linked.

What happens if you run the same command but with the following env var:

CONDA_NOTIFY_OUTDATED_CONDA=false conda install ...

The next release of conda-libmamba-solver won't rely on conda internals for this update-detection logic, but for now let's see if you can work around the issue with the above approach!

from conda-libmamba-solver.

Just checking in, is this still happening with the latest release of conda-libmamba-solver?

from conda-libmamba-solver.

Technically we default back to conda for non-standard channels, but I can't test against that on-prem-nexus-protocol :/

from conda-libmamba-solver.

This should be solved (?) by #65

from conda-libmamba-solver.

With #65 all networking happens via conda, so this shouldn't happen, and if it does, it will also affect conda with solver=classic.

It could also be linked to #146.

I am inclined to close with #168, but please feel free to reopen if it still happens once the new version is out.

from conda-libmamba-solver.

Agreed, it would obviously be great to get feedback once 23.3.0 is out. Thank you!

from conda-libmamba-solver.

Closing via #168

from conda-libmamba-solver.