-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Cannot execute cell or save Jupyter Notebook in remote VS connection opened with showNotebookDocument API #119891
Comments
Can you give some more details about what you are doing and what's going wrong? |
Do you have the latest version of the jupyter extension installed on your remote? |
I have latest insiders for Jupyter 2021.5.685944597. I tried with latest stable Jupyter 2020.11.399280825 but jupyter fails to activate. |
Why does this document URI have the file scheme? Is it a local document? Did you open it with a file URI? |
That's something we don't understand since we are opening with "vscode-remote://amlext/home/azureuser/cloudfiles/code/test.ipynb" |
It's working fine for me. Could you run "Set Log Level" > Trace, run the scenario again, and share the log from the Log (Window) output channel? |
@roblourens were you able to repro and have it working for AML remote or is this with a different remote extension? |
I was just trying it with the SSH extension, I don't know why it would be different. In your log @sevillal it looks like it ends with just opening the notebook. Did you try to save and get the same error this time? |
@roblourens I noticed the following behavior:
But, if I don't run the cell first I can change and save the document without issues. Attaching log with the saving error: |
Cc/ @DonJayamanne for visibility |
Apologies if this information has already been provided. @roblourens from what i can tell,
This following error is interesting
Here are the logs when it fails (Logs from Jupyter Extension)
Here are the logs when the notebook was opened from file explorer & things work (Logs from Jupyter Extension)
|
@roblourens I was able to repro with remote-ssh extension by opening the file as we do in azureml extension (maybe we are not opening it the right way) Here the change I tested: https://github.com/sevillal/vscode-remote-ssh/commit/3042b2c18ff8b0a1f9350d85b72c4fb4eecd9fd6 |
That is not a valid URI, I'm not even sure why it opens the notebook. It's missing the host. I can repro with that URI but not a well-formed URI that includes the host. Example vscode.window.showNotebookDocument(vscode.Uri.parse('vscode-remote://ssh-remote%2bmyhost/path/to/notebook'), {
preserveFocus: false,
preview: false
}); I am sure this has nothing to do with remote, and is just the result of passing the wrong URI. Try this
|
In your AML scenario, try comparing the URI of the editor that is opened when you click that file in the explorer, to the URI that you pass to showNotebookDocument. I think VS Code is too tolerant in something, and we don't fail until you try to save. |
Thanks for the suggestion @roblourens. We're wondering how to get the URI for files that are manually opened? Is that logged somewhere or do we need to add something ourselves? |
You can read the |
@roblourens we were able to see the right behavior after using the same URI format as in vscode.notebook.notebookDocuments, thanks for all your help! Before closing this issue the team will test the change in stable 1.55 just to confirm is working fine for everybody. |
ping @sevillal - can this be closed? |
Steps to Reproduce:
Full log attached.
full_log.txt
notificationsAlerts.ts:40 Failed to save 'test.ipynb': NO notebook document for 'file:///home/azureuser/cloudfiles/code/test.ipynb' onDidChangeNotification @ notificationsAlerts.ts:40 console.ts:137 [Extension Host] Kernel: connected (e2434543-78ef-4522-969d-c701497f1f15) console.ts:137 [Extension Host] Starting WebSocket: ws://localhost:8891/api/kernels/147d0cee-7924-402f-97d0-383ba5c2da51 console.ts:137 [Extension Host] Kernel: connected (147d0cee-7924-402f-97d0-383ba5c2da51) log.ts:296 ERR Invalid uri, not a notebook: /home/azureuser/cloudfiles/code/test.ipynb: Error: Invalid uri, not a notebook: /home/azureuser/cloudfiles/code/test.ipynb at s.getTextDocumentWrapper (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:61:198474) at s.toOutgoingDocument (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:61:192283) at t.NotebookMiddlewareAddon.provideHover (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:61:186794) at y.callNext (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:9:431693) at y.provideHover (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:9:429657) at y.o.value (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:9:432312) at Object.provideHover (/home/azureuser/.vscode-server-insiders/extensions/ms-python.python-2021.3.680753044/out/client/extension.js:9:136682) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:86:159486 at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:64:12046 at new Promise (<anonymous>) at g (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:64:12018) at l.provideHover (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:86:159466) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:86:182161 at Ie._withAdapter (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:86:178959) at Ie.$provideHover (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:86:182137) at u._doInvokeHandler (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:90:12794) at u._invokeHandler (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:90:12478) at u._receiveRequest (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:90:11094) at u._receiveOneMessage (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:90:9931) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:90:8032 at b.fire (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:57:1836) at E.fire (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:65:15496) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:105:29935 at b.fire (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:57:1836) at E.fire (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:65:15496) at t._receiveMessage (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:65:20754) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:65:17640 at b.fire (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:57:1836) at acceptChunk (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:65:12861) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:65:12209 at b.fire (/home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:57:1836) at /home/azureuser/.vscode-server-insiders/bin/6f726bcdf6a4d6cb518a3fcdb03c21be7293f417/out/vs/server/remoteExtensionHostProcess.js:105:18820 at afterWrite (_stream_writable.js:490:5) at onwrite (_stream_writable.js:470:7) at InflateRaw.afterTransform (_stream_transform.js:98:3) at Zlib.processCallback (zlib.js:578:8)
The text was updated successfully, but these errors were encountered: