Repository Issue Activity (beta)

#4375 BUG: `shell init` incorrectly detects Nushell when parent process name contains substring "nu" (which appears in the word "linux")

#4393 Track conda-forge win-arm64 packages needed to drop environment-dev-win-arm64.yml

#4394 [libmamba] Per-package repodata `url`/`urls` are discarded: `set_solvables_url` overwrites every solvable's URL with the channel-derived one

#1885 Mamba does not include configured subdirs in package search

#4230 micromamba.exe has no output in windows 11.

#4377 Check `(micro)mamba` execution after `shell hook`

#4392 Long path support not enabled on AppVeyor with 2.9

#4275 Change of pkgs cache directory made it go over the windows limit

#4391 `--always-softlink` fails when linking packages containing existing files

#4389 Security warning should mention which package executes package scripts

#4154 BUG: mamba update --file does not take into account file changes

#4374 `env export --from-history` fails with a JSON parse error on history entries with comma-range specs (regression in 2.9.0)

#4077 Silent failure on Window after "shell hook"

#4322 "Invalid package cache" ruins installed env

#4235 Porting xonsh hook fixes from conda to mamba

#4378 Crash when Python interpreter shuts down

#4351 New release would be great

#4372 Check/Add specific tests

#3879 `mamba activate` fails in Windows after starting cmd.exe with `activate.bat`, shell not initialized

#4263 Surprisingly hard environment specification to solve for `libsolv`

#4156 BUG: mamba does not apply repodata patches for already-downloaded packages

#4002 Why does mamba need to set permissions on pkgs/cache? This prevents the use of a shared cache directory in a multiuser environment.

#3740 critical libmamba filesystem error: cannot set permissions: Operation not permitted

#4014 error libmamba Could not solve for environment specs

#3970 Resolving environment with Python 3.13 takes very long time