It's nice that the installation instructions are pretty ting, and that the process is simple. But, I feel these could be epxanded for when things go wrong...:
I'm trying to launch a notebook from within VS Code. I'll take the web interface if that's all that will work right now, but, as it's nice to step through in a debugger, and I have used VS Code for PYthon notebooks before, I started there. The kernel doesn't seem to launch fully, so I then broke open a shell to look at what is going on.
It may not be critical, but I get a segfault when I just try to run xcpp --help, so that feels something to be sorted first.
The C library still seems to be coming form my system - If I include the logs form VS Code, you can see a warning about possible version mismatch:
19:16:25.956 [info] Dispose Kernel '/tmp/Xeus Demo Notebook.ipynb' associated with '/tmp/Xeus Demo Notebook.ipynb'
19:16:25.956 [info] Dispose Kernel process 1976825.
19:17:28.608 [info] Start refreshing Kernel Picker (1695151048608)
19:17:28.732 [error] Failed to get activated conda env vars for /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11
in 110ms
19:17:28.732 [error] Unable to determine site packages path for python /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11 (Conda)
19:17:28.752 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11 -m pip list
19:17:29.626 [info] End refreshing Kernel Picker (1695151048608)
19:17:37.822 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11 -c "import jupyter;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
19:17:37.842 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11 -c "import notebook;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
19:17:37.874 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11 -m jupyter kernelspec --version
19:17:38.030 [warn] No interpreter with path /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python found in Python API, will convert Uri path to string as Id /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python
19:17:38.081 [info] Start refreshing Kernel Picker (1695151058081)
19:17:38.118 [error] Failed to get activated conda env vars for /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python
in 32ms
19:17:38.118 [error] Unable to determine site packages path for python /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python (Conda)
19:17:38.132 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python -c "import jupyter;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
19:17:38.151 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python -c "import notebook;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
19:17:38.180 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python -m jupyter kernelspec --version
19:17:39.089 [info] End refreshing Kernel Picker (1695151058081)
19:17:46.728 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python -m pip list
19:17:46.741 [info] Starting Kernel startUsingLocalKernelSpec, .jvsc74a57bd01d18f535d0bd82abaafaf8716b7e7ed95b2db33560c5e28c2b34d69938f72741#xcpp17./media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11././media/<username>/sdb_ext4/users/<username>/micromambaroot/envs/xeus-clingbugreport/bin//xcpp#-f#{connection_file}#-std=c++17 (Python Path: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11, Conda, 3.11.5) for '/tmp/Xeus Demo Notebook.ipynb' (disableUI=true)
19:17:46.754 [info] Launching Raw Kernel C++17 # /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin//xcpp
19:17:46.788 [error] Failed to get activated conda env vars for /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11
in 33ms
19:17:46.788 [error] Unable to determine site packages path for python /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin/python3.11 (Conda)
19:17:46.819 [info] Process Execution: /media/<username>/SDB_EXT4/Users/<username>/MicromambaRoot/envs/Xeus-ClingBugReport/bin//xcpp -f ~/.local/share/jupyter/runtime/kernel-v2-1962684VSFBFJ9Gpqah.json -std=c++17
> cwd: /tmp
19:17:47.368 [warn] StdErr from Kernel Process registering handler for SIGSEGV
19:17:50.098 [warn] StdErr from Kernel Process Starting xeus-cling kernel...
If you want to connect to this kernel from an other client, you can use the ~/.local/share/jupyter/runtime/kernel-v2-1962684VSFBFJ9Gpqah.json file.
19:17:50.098 [warn] StdErr from Kernel Process Run with XEUS 3.1.1
These <username>s are in the VS Code logs; I haven't redacted the path (as I have in the others), so need to work out what is going on there.
To do this for a clean MRE, I had to install python and the notebook package inside this environment - it seems VS Code wasn't happy finding the Xeus kernel without having a python interpreter in the mamba environment PATH I could point it to first.
Hi,
It's nice that the installation instructions are pretty ting, and that the process is simple. But, I feel these could be epxanded for when things go wrong...:
I'm trying to launch a notebook from within VS Code. I'll take the web interface if that's all that will work right now, but, as it's nice to step through in a debugger, and I have used VS Code for PYthon notebooks before, I started there. The kernel doesn't seem to launch fully, so I then broke open a shell to look at what is going on.
It may not be critical, but I get a segfault when I just try to run
xcpp --help, so that feels something to be sorted first.The C library still seems to be coming form my system - If I include the logs form VS Code, you can see a warning about possible version mismatch:
These
<username>s are in the VS Code logs; I haven't redacted the path (as I have in the others), so need to work out what is going on there.To do this for a clean MRE, I had to install python and the notebook package inside this environment - it seems VS Code wasn't happy finding the Xeus kernel without having a python interpreter in the mamba environment PATH I could point it to first.
then, I needed to re-install xeus-cling:
Any advice? Is the backtrace a bug, or have I missed installing somehting essential, is micrommaba officially supported?
Thanks a lot!!