[micromamba] Using --json for `micromamba create` eats up all error messages

[romain-intel]

If there is an error in creating an environment and you use the --json option, the error is not reported back. Worse, the returned JSON says "success": true. micromamba does return a non-zero code but any error is gobbled up.

[aspyk]

Same problem with the json here.
In my case if a package is not available in a list of packages, while conda returns (among others infos) the type of error and the name of the bad package like this:

conda install --json bad_package 

{
 [...]
  "exception_name": "PackagesNotFoundError",
  "packages": [
    "bad_package"
  ],
}

mamba returns just the following json:

mamba install --json bad_package

{
    "success": false
}

[romain-intel]

at least the success is set to false :).

[romain-intel]

any updates on this? Thanks!

[jonashaag]

Do you want to try to come up with an initial fix?

[Klaim]

I'm working on this related pr #4202
While working on #4126 , I saw that issue too, and found out that the error logging was overwritten by the json output.

One possible improvement I could do as part of #4202 or a followup PR would be to gather error logs separately and inject these into the JSON output in a special member, to help with debugging.

Would that be helpful?