Closed tbenst closed 3 years ago
@tbenst, It looks like you may have been accidentally been entering the correct URI in the interactive case? It appears that "https://hostname" may have been entered by mistake.
@greazer no, I am pasting the same value in both cases
@tbenst can you check this setting:
python.dataScience.jupyterServerUri
It should point to the URI you want. The 'Select local or remote Jupyter server for connections' just sets this setting.
Your error output is indicating it wasn't set.
@rchiodo the setting is set correctly. It fails when I try running a cell in the .py file. But as soon as I try running a cell in a .ipynb file, connection succeeds, and I can subsequently run cells in a .py file.
What is the failure that it generates?
@rchiodo I documented the failure in my original post, including the popup in bottom right corner + developer tools console. Please let me know if I can provide additional info that would be helpful. Thanks for your help!
Can you upload the entire developer tools console? The console output you uploaded looks to be just the last cell running.
The error message you originally posted:
Failed to connect to remote Jupyter notebook.
Check that the Jupyter Server URI setting has a valid running server specified.
https://hostname:8080/ TypeError: request to https://hostname:8080/api/contents/?1594362020681 failed,
reason: getaddrinfo EBUSY hostname
Did you change it all? https://hostname:8080 would not work, but maybe you changed it to protect your host name. If you didn't change it looks like the default value we use as an example for the specify server command.
@rchiodo I did not change the messages at all. Here are the full logs. Note that I run a cell in the second notebook at 2020-07-15 08:04:53
.
```
[Extension Host] Info Python Extension: 2020-07-15 08:04:42: Waiting for jupyter server and web panel ...
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Loading web panel. Panel is notset
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Loading web view...
console.ts:137 [Extension Host] Warn Python Extension: 2020-07-15 08:04:42: startHttpServer=false, will not be used. Temporarily turned off
t.log @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:582
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:582
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Web view created.
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Getting jupyter server options ...
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Connecting to jupyter server ...
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Connecting to history server
console.ts:137 [Extension Host] Info Python Extension: 2020-07-15 08:04:42: Cached data exists getEnvironmentVariables,
Looks like a different error in the log:
http://localhost:8880/ Error: Invalid response: 500 Internal Server Error
Not sure why it would fail on the first attach and work on the second.
Does the output of the jupyter server indicate anything? It should have put out a bunch of messages to stderr where you started it.
Steps to cause the bug to occur
ssh -L 8888:localhost:8888 myserver
jupyter notebook
Note that this exact procedure succeeds if you open an .ipynb file instead!
Your Jupyter and/or Python environment
Developer Tools Console Output
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl