I do not have this problem with Conda, just with Mamba
Describe your issue
This comes from the conda-lock test suite when using micromamba v2.0.4.
In short, whenever Micromamba prints a channel URL to the console and that URL contains a token, it censors the token by replacing it with *****. The regression here is that when Micromamba requests a URL from the Conda channel server, the token is sent as ***** instead of its original value, so Micromamba is making invalid requests.
The input to micromamba is this explicit lockfile:
Search tried in issue tracker
token
Latest version of Mamba
2.0.4a3
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
This comes from the conda-lock test suite when using micromamba v2.0.4.
In short, whenever Micromamba prints a channel URL to the console and that URL contains a token, it censors the token by replacing it with
*****
. The regression here is that when Micromamba requests a URL from the Conda channel server, the token is sent as*****
instead of its original value, so Micromamba is making invalid requests.The input to micromamba is this explicit lockfile:
/tmp/explicit.txt
:To monitor what's going on, run
If I run
then I get warnings and an error:
The webserver shows that the token is being censored in the URL:
When I replace
micromamba
withconda
, you see the token being logged by the webserver:If I downgrade to 2.0.2 then the token is sent.