search

conda-forge / notebook-feedstock

A conda-smithy repository for notebook.
BSD 3-Clause "New" or "Revised" License
3 stars 34 forks source link

Jupiter Notebook not working under M1 mac OS 11.1 #85

Closed Johannes-Lange closed 2 years ago

Johannes-Lange commented 3 years ago

After ˋconda install notebook´ into my conda environment and starting it once, the whole environment is broken. When running python from the terminal, I get the message ˋzsh: killed´, my IDE shows ˋprocess was killed by SIGKILL (Signal 9)´. Uninstall the package doesn't fix this, I tried to create a new environment, this also doesn't work due to ˋzsh: killed´.

bollwyvl commented 3 years ago

The full output of conda list --explicit and conda info --json, redacted, if there's any sensitive paths, etc. would be very helpful, if it is capable of running those.

That being said: much like the architecture itself, conda-forge's M1 support is still very new, and cross-compiled to boot... there are some related things (e.g. https://github.com/conda-forge/ipython-feedstock/pull/129) which may be related, but we're kinda throwing darts here.

erykoff commented 3 years ago

It is possible that this is related to the above bug, but I know that I have successfully run jupyter notebooks when we did the port. I will see if I can replicate.

erykoff commented 3 years ago

@Johannes-Lange I'll need more info. Just now I was able to successfully make a new notebook env on both python 3.8 and 3.9 and everything worked as expected. This zsh: killed is usually a sign of a code signing error. As far as I know these have all been ironed out, but there's always the possibility that something went wrong on installation and corrupted a file.

bollwyvl commented 3 years ago

Oooh, if you downloaded miniforge/mambaforge through your browser, that could trigger it, no? Grabbing it with curl might work better.

erykoff commented 3 years ago

Ah, that shouldn't be an issue. The binaries that are downloaded are signed (as well as the binaries and libraries built and distributed). However, when things are installed the rpaths all have to be changed for the local installation, and this modification requires a re-signing of everything on install.

Anyway, for this particular problem I think I need to know the exact list of packages in the environment.

Johannes-Lange commented 3 years ago

Unfortunately I hadn't much time to get all these. This occurred on two M1s, both with miniforge and an conda environment (only numpy, Pandas, pytorch and jupyter). On one Computer Jupyter has been working for weeks but yesterday (I think after MacOS 11.1 update) this error occurred after starting jupyter notebook. I then installed notebook on the other M1 to check if it's reproduceable and after starting it gave me the same zsh message.

erykoff commented 3 years ago

I don't believe pytorch has been ported to osx-arm64 yet, at least on the main channels. Are you using the experimental one from -c isuruf/label/pytorch or are you running x86 under rosetta?

Johannes-Lange commented 3 years ago

I built it myself from the main branch. But this wasn’t the problem since the other M1 hasn’t installed it.

Von meinem iPhone gesendet

Am 03.02.2021 um 16:53 schrieb erykoff notifications@github.com:

 I don't believe pytorch has been ported to osx-arm64 yet, at least on the main channels. Are you using the experimental one from -c isuruf/label/pytorch or are you running x86 under rosetta?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

erykoff commented 3 years ago

Thanks. So far I'm unable to replicate. What version of conda are you using?

erykoff commented 3 years ago

Also, the new build of ipython is available, if for any reason that was related.

Johannes-Lange commented 3 years ago

miniforge3-4.9.2-4 and then the packages all installed directly into one environment, not the base.

Am 03.02.2021 um 17:00 schrieb erykoff notifications@github.com:

 Thanks. So far I'm unable to replicate. What version of conda are you using?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

erykoff commented 3 years ago

I just did conda create -n nbtest5 python=3.9 pandas notebook numpy and was able to start ipython, python, jupyter notebook, etc, and successfully import numpy and pandas, quit the notebook, and start both python and ipython. I'm not sure what to look at now, but let me know if I'm missing something.

jakirkham commented 3 years ago

Johannes, maybe it would help if you could share a reproducer? Admittedly this may be hard to generate, but it would make debugging much more straightforward

bollwyvl commented 3 years ago

All builds from https://github.com/conda-forge/ipython-feedstock/pull/130 are up. Please test!

bollwyvl commented 2 years ago

Please re-open if additional issues occur.