-
Notifications
You must be signed in to change notification settings - Fork 293
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
Run Cells Cannot launch Jupyter #3190
Comments
This is a path problem with our conda activation. Not specific to datascience I believe. |
@awbruch I believe you can workaround this problem by starting VS code from the conda prompt. |
@rchiodo Just ran a couple tests and the workaround seems to work for me. Thanks for the help! Is there a timeline for a long-term fix or should I just stay tuned and check after VSCode updates? |
Not sure if we're going to be able to fix it or not. We can't repro it in house yet. I suspect we're not setting paths correctly for some reason, but it seems to work just fine on all of our local machines. The only way I can think of fixing this would be to deliver private bits to people experiencing the problem and add a bunch more logging until we can determine the root cause. So to answer your question, I think it's going to be a while. |
@DonJayamanne I don't believe this is a datascience issue. It's a conda activation issue. |
Okay thanks. Running from the command prompt is not an absolute deal-breaker right now. Is there anything I can supply/try on my end that could help be of more diagnostic help? |
If you're willing to try the insider's build, I can try adding a bunch of extra logging to it. Probably take me an hour or so. |
Oh and before we do that, can you go to the conda env you're using and run 'conda info' and put the results here. Here's what mine says:
|
Here is the output of
|
Okay I submitted a change that should at least log all of the environment variables we set before trying to start jupyter. If you install the insider's build (install from the Extensions tab's ... button) and repro the issue, we can compare the environment we generate to your normal conda environment. No rush though. Whenever you get the chance. |
Sorry should have said it takes about an hour for the insider's build to finish. So an hour from now the logging change will be there. |
I believe there is a difference between how the windows path is set when activating an environment created in a miniconda environment vs an anaconda environment. Miniconda's conda.bat (last I checked) will not update the windows path to find needed dll's for some python packages. Anaconda's will. |
I'm reproing this now with miniconda. I get the same dll load failure. So one workaround is to not use miniconda, but the full anaconda distribution. |
Ah okay, good to know where this is coming from then. Looking at microsoft/vscode-python#5792, there might be a lot of moving parts from (mini)conda and Jupyter to get a long-term fix in place right now. It might best to stick with either workaround for now. Thanks for looking into this on so many fronts. Would you still like to see the logs from my machine? |
No that's okay. I can repro locally so that should be good enough. Thanks for the help. |
Wow thanks, that was super quick! I will just pick up the new changes with the next release since we have decent temporary fixes in place. Thanks for everything that you all are doing, VSCode has been hugely helpful to my work and it's only getting better! |
Environment data
Version: 1.36.1 (user setup)
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:59:35.033Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17763
Expected behaviour
Run cell to send code to Python Interactive Window
Actual behaviour
Running Cell fails and raises error "Running Cells requires Jupyter notebooks to be installed"
Note: running command
python -m jupyter notebook --version
in integrated terminal works fine, and returns6.0.0
. Also confirmed that launching jupyter notebook from terminal works fine.Behavior is very similar to microsoft/vscode-python#5102 and microsoft/vscode-python#6763, not sure if related to recent Python 3.7.3 upgrade. Log from developer tools is attached below.
Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: