-
Notifications
You must be signed in to change notification settings - Fork 294
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
not able to start jupyter notebook imported into python using wsl when running as the root user #1124
Comments
This may be a problem with an out of date jupyter. Can you try this from the same python environment and respond with the results? Additionally if you could goto 'Help | Toggle Developer Tools', click on the console tab, right click save as, and upload the log, that would help too. |
This may also be related to our default config we specify for jupyter. See this similar issue here: |
here's what i get with the jupyter version running from the vscode terminal
attached is the console log |
I tried toggling |
That console log doesn't have everything in it. It looks like you only uploaded the errors? Hopefully jupyter output something else that can show us what the problem is. Error code 1 is EPERM, so perhaps your jupyter is configured to require a password. |
For the password, I took a look in the jupyter_notebook_config.py and see the following line is commented out. #c.NotebookApp.password = '' . Not sure where else to look for password settings. I can launch jupyter from the command line and view in a browser w/o password. I clicked on the console->messages and updated the gist above. However, looking at it, I didn't see anything useful. :( In vscode, I went to output -> Python to look at the logs for jupyter and added a gist here. https://gist.github.com/foobar8675/6caf97a4014795c505cb80f67c1a3b45 In looking at it, I'm not sure I see what a problem might be |
That's still not the right console log. That looks like the output from the python tab of the 'output' window. The console log is what you're showing in your screenshot above, you're just only showing errors. It should be rather large. This is what mine looks like: |
I should also mention that a normal jupyter notebook isn't running the same way as us. We're closer to jupyter lab. We talk to the tornado server that jupyter starts up. That's likely where the problem is. Hopefully Jupyter is outputting something telling us why it's crashing. |
Thanks for clarifying for the logs. I'll regenerate that log file tonight when I'm back on that computer. I also didn't know jupyter ran Tornado under the hood. I've been looking at Starlette but will also look at Tornado. |
i just generated a new log which is here. https://gist.github.com/foobar8675/87bd0d2f2047840ed500af0f3fbf6e9f and noticed one line that looked suspicious.
so i ran this with the following output
then ran this
which seemed ok. so i tweaked my and it seemed to work! Did I miss something in the instructions about not using a root user? |
No we don't specify that anywhere. I should add that to our list of stuff to check. We've hit this before with docker containers, so we auto detect docker and pass the --allow-root flag. Glad you got it working. I'm going to change this bug to detect root access and/or update our docs to say don't run as root. |
Got it and thank you for all your help @rchiodo . I'm not sure if this issue should stay open or closed? |
I'd like to leave it open so we can check for root access and warn the user. Thanks. |
this fixed issue with root remote connection to start jupyter via vscode - remember to restart vscode after changing 'default config for jupypter' |
Using raw kernels should fix this, i.e. ensure we have zeromq support |
@Qiuzhuang sorry for not getting back to you on this. wanted to check if this is still unresolved? |
Yes, this is working perfectly now. Thank you. |
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version vscode-python#3977): jedi, but happens both waysExpected behaviour
Actual behaviour
run cell for this
gives
Steps to reproduce:
see error message
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)i wasn't able to find
Enable source map support for extension debugging
advice?The text was updated successfully, but these errors were encountered: