vscode: Notebooks cannot be opened on 1.59
Issue Type: Bug
Visual Studio Stable version doesn’t open notebook (ipynb) files as anything but text.
I get this error in the developer tools console:
[vscode.ipynb]: Notebook type 'jupyter-notebook' already used.
VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:12.822Z) OS version: Windows_NT x64 10.0.19043 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i7-8700 CPU @ 3.20GHz (12 x 3192) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 63.85GB (48.37GB free) |
| Process Argv | –crash-reporter-id 2900f695-595f-4fc6-a76e-3da9117b78c6 |
| Screen Reader | no |
| VM | 0% |
Extensions (12)
| Extension | Author (truncated) | Version |
|---|---|---|
| prettier-vscode | esb | 8.1.0 |
| python | ms- | 2021.9.1137256656-dev |
| vscode-pylance | ms- | 2021.8.2-pre.1 |
| jupyter | ms- | 2021.8.1236758218 |
| remote-containers | ms- | 0.191.1 |
| remote-ssh | ms- | 0.65.7 |
| remote-ssh-edit | ms- | 0.65.7 |
| remote-wsl | ms- | 0.58.2 |
| vscode-remote-extensionpack | ms- | 0.21.0 |
| vscode-typescript-tslint-plugin | ms- | 1.3.3 |
| debugger-for-chrome | msj | 4.12.12 |
| typescript-hero | rbb | 3.0.0 |
A/B Experiments
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
vsdfh931:30280409
vshan820:30294714
vscod805:30301674
bridge0708:30335490
dockerwalkthru:30344881
bridge0723:30353136
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 15 (12 by maintainers)
I saw the advice to delete
AppData\Roaming\Code\User\globalStorage\state.vscdb(search for %appdata% in Windows 10) before the suggestion to just remove thememento/notebookEditorskey from it (it’s a sqlite db?). This did resolve the issue but only after re-granting workspace trust - hope you manage to get the fix into a new release soon!