-
-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes using mamba
on macOS Sonoma
#512
Comments
Just came across this. It seems to affect any attempt to install a package using mamba. Here's relevant snippets of output from a simple command Output
|
Same problem. |
This crash is typically because some library loaded (here, probably So this should be fixed by moving to curl >= 8.4.0 |
Does it work with This should be the same (
|
I'm afraid I don't have access to a Sonoma machine, so cannot be of much use. However I am still getting reports of this occurring with the latest Mambaforge (23.11.0). Confusingly I am also getting reports of successful installations on Sonoma, so there is another factor at play somewhere. We have solved this issue in our system by switching to the latest Miniconda release (also versioned 23.11.0), and calling For what it's worth, here is a log file of our installer script which uses mambaforge to set up a conda environment containing our software, in which the error has occurred. The installer does the following:
Note that our installer script is written in Python, and so a separate Python interpreter is required to run our script and to bootstrap the installation. One common theme amongst all of the reports I have received are that the Python interpreter used for running the installer script is an Anaconda installation (e.g. I had a wild theory that perhaps the Anaconda installation has an out-dated libcurl library, and that this library is somehow magically being loaded by the mambaforge Python interpreter, instead of the one installed into the mambaforge base environment. I asked a colleague of mine (with a M1 mac running Sonoma) to test this theory (install an old version of Anaconda with a broken libcurl, then use it to run our installer), but he wasn't able to reproduce the error. So I'm kind of stumped. But as I mentioned, this is not a problem for us, as with the switch to miniconda our users are no longer experiencing the error. |
Solution to issue cannot be found in the documentation.
Issue
Howdy,
(Reporting here for posterity - I think the main issue is curl/curl#11893).
I have a couple of users reporting crashes when running
mamba env update
on macOS Sonoma. I don't have access to a Sonoma machine, so can only provide a few more details (if necessary), but I think the most relevant message that is emitted is:Searching around the internet, I stumbled across a recently fixed issue in
curl
.So I suspect that this issue will be resolved with a new miniforge/mambaforge release that bundles the latest curl 8.4.0.
Judging by #511, it sounds like this is already on the cards, so hopefully this be resolved without any further effort.
Thanks!
Installed packages
Environment installed via [`Mambaforge-23.3.1-1-MacOSX-arm64.sh`](https://github.com/conda-forge/miniforge/releases/download/23.3.1-1/Mambaforge-23.3.1-1-MacOSX-arm64.sh)
Environment info
Environment installed via [`Mambaforge-23.3.1-1-MacOSX-arm64.sh`](https://github.com/conda-forge/miniforge/releases/download/23.3.1-1/Mambaforge-23.3.1-1-MacOSX-arm64.sh)
The text was updated successfully, but these errors were encountered: