Skip to content
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

Command 'Create new jupyter notebook' resulted in an error #167779

Closed
roblourens opened this issue Nov 30, 2022 · 2 comments
Closed

Command 'Create new jupyter notebook' resulted in an error #167779

roblourens opened this issue Nov 30, 2022 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) notebook-serialization

Comments

@roblourens
Copy link
Member

roblourens commented Nov 30, 2022

Testing microsoft/vscode-jupyter#11963

This is familiar, there might be an issue for this, but I'm not sure and can't find it

I just ran the command and closed the new untitled notebook over and over then got this

image

2022-11-30 15:50:58.937 [error] NO notebook document for 'untitled:Untitled-2.ipynb?jupyter-notebook': Error: NO notebook document for 'untitled:Untitled-2.ipynb?jupyter-notebook'
    at f.getNotebookDocument (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:96:78756)
    at k.$acceptDirtyStateChanged (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:86:107708)
    at u.N (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:11208)
    at u.M (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:10926)
    at u.H (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:10019)
    at u.G (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:9000)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:7788
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at h.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:14314)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:120:15804
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at h.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:14314)
    at c.y (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:17324)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:15795
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at g.acceptChunk (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:12045)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:11332
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at g.t (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:25895)
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-jupyter Nov 30, 2022
@rebornix rebornix added the bug Issue identified by VS Code Team member as probable bug label Dec 1, 2022
@rebornix rebornix assigned roblourens and unassigned DonJayamanne Dec 1, 2022
@rebornix
Copy link
Member

rebornix commented Dec 1, 2022

From the log it seems related to our model syncing

at f.getNotebookDocument (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:96:78756)
    at k.$acceptDirtyStateChanged

@rebornix
Copy link
Member

A dup of #148368

@rebornix rebornix added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 20, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Feb 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) notebook-serialization
Projects
None yet
Development

No branches or pull requests

3 participants