micromamba is not recognized as an internal or external command 2.0.0

[ktsitsi]

Yesterday we noticed a failure in our CI only on the windows-latest runner where we were getting the following error:

'"C:\Users\runneradmin\micromamba\condabin\micromamba"' is not recognized as an internal or external command,
operable program or batch file.

using the mamba-org/setup-micromamba@v1. while running a simple pre-commit check using the env.

Run micromamba run -n test pre-commit run -a

Taking a look at the logs the only difference we notice is that micromamba info
was now fetching

libmamba version : 2.0.0
micromamba version : 2.0.0

We were able to resolve by pinning to mamba-org/setup-micromamba@v1.9.0 with the micromamba-version: 1.5.10-0 following similar approach as commented in #225

Runner Logs here

[jeremyleung521]

Was hoping mamba=2.0.1 would fix this (there was a fix for a windows bug on mamba activate), but that doesn't seem to be case. Not sure if this is a problem on setup-micromamba's end or regular mamba's end?

Runner Logs: https://github.com/jeremyleung521/LPATH/actions/runs/11088430490/job/30931937962#step:4:362
Note: Can't see that it's running 2.0.1 in the windows jobs due to the order things are printed, but the other tests (macos, ubuntu) do say that 2.0.1 is pulled.

EDIT: It's being tracked here: mamba-org/mamba#3478

[pavelzw]

i would expect that this is a micromamba issue. wdyt @jjerphan?

[jjerphan]

It is. There's a problem with the activation script on Windows as of micromamba 2.0. We are currently addressing the problem.

[jjerphan]

2.0.2 is being released and should fix this issue.

[jeremyleung521]

2.0.2 is being released and should fix this issue.

Thank you! Just have to wait for micromamba-releases to update, then should be able to test!

[jeremyleung521]

I just updated to v2 (2.0.2) and still having the same problem... :/ Though this time, it's failing in the 'pip' section of the environment file.

 Or to execute a single command in this environment, use:
  
      micromamba run -n test mycommand
  
  warning  libmamba You are using 'pip' as an additional package manager.
      Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
  
  Installing pip packages: pylcs, ray, timedinput, argparse-tui
  '"C:\Users\runneradmin\micromamba\condabin\micromamba"' is not recognized as an internal or external command,
  operable program or batch file.
  critical libmamba pip failed to install packages

Log file: https://github.com/jeremyleung521/LPATH/actions/runs/11182636779/job/31089361519#step:4:370

EDIT: It's this bug: mamba-org/mamba#3467.

[jjerphan]

#234 resolved the cause of the problem.

Updating setup-micromamba to 2.0.0 should resolve the issue.

[jeremyleung521]

#234 resolved the cause of the problem.

Updating setup-micromamba to 2.0.0 should resolve the issue.

Unfortunately it doesn't :( It works fine installing the conda packages, but I eventually get to the same error while trying to install the pip packages from the environment file. It's this error: mamba-org/mamba#3467.

Logs: https://github.com/jeremyleung521/LPATH/actions/runs/11218580614/job/31182684438?pr=10#step:4:348

[ika-musuko]

I don't really know if this is good or not, but as a temporary fix, I copied the already existing mamba.bat to micromamba.bat inside the directory provided in the error, and was able to install packages from pip.

e.g. in my case I got this error:

'"C:\Users\ika\AppData\Roaming\mamba\condabin\micromamba"' is not recognized as an internal or external command,
operable program or batch file.
critical libmamba pip failed to install packages

In PowerShell, I did the following

PS C:\> cd C:\Users\ika\AppData\Roaming\mamba\condabin
PS C:\Users\ika\AppData\Roaming\mamba\condabin> ls

    Directory: C:\Users\ika\AppData\Roaming\mamba\condabin

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          2024/10/29    18:02           1911 _mamba_activate.bat
-a---          2024/10/29    18:02            142 activate.bat
-a---          2024/10/29    18:02            778 mamba_hook.bat
-a---          2024/10/29    18:02            851 mamba.bat
PS C:\Users\ika\AppData\Roaming\mamba\condabin> cp mamba.bat micromamba.bat

Then I went back to the original directory, reran the micromamba create env command and everything worked fine.

This is a little perplexing though because on the surface it looks like the installer script copies a micromamba.bat file into the install location though...

setup-micromamba/src/shell-init.ts

Line 40 in 617811f

const copyMambaBatToMicromambaBat = (options: Options) => {

But this copyMambaBatToMicromambaBat function does not seem to be getting called anywhere in the codebase...so not sure what's going on