Vscode-jupyter: Unable to open Jupyter Notebooks: Using the Jupyter notebook editor requires the stable version of VS code and the CustomEditor experiment to be enabled..

[xcojonny]

Environment data

• VS Code version: 1.51.1
• Extension version (available under the Extensions sidebar): XXX
• Jupyter Extension version (available under the Extensions sidebar): v2020.11.372831992
• OS (Windows | Mac | Linux distro) and version: Win10
• Python and/or Anaconda version: Python 3.8.1
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Jupyter server running: Local and Remote

Expected behaviour

Clicking on a Jupyter-Notebook opens the notebook.

Actual behaviour

Clicking on a Jupyter-Notebook opens the Notebook for a second. Then the file is being closed and the following error is displayed:
Unable to open '[*].ipynb': Using the Jupyter notebook editor requires the stable version of VS code and the CustomEditor experiment to be enabled..

This behaviour occurred suddenly, without me changing knowingly anything in VSC. The Notebooks can still be opened on different machines. Furthermore creating a new Notebook works.

Steps to reproduce:

1. Try to open any jupyter notebook within VSC over the side bar -> Leads to error
2. Opening via terminal (code file.ipynb) -> Leads to error

Logs

User belongs to experiment group 'jupyterTest'

[takotab]

Same issue on ubuntu 20.04

[rchiodo]

@claudiaregio this might be a side effect of the custom editor experiment being turned on.

[rchiodo]

This shouldn't be happening but might be caused by this setting being in your user settings.json:

    "workbench.editorAssociations": [
        {
            "viewType": "jupyter.notebook.ipynb",
            "filenamePattern": "*.ipynb"
        }
    ],

Can you check if that editor association is there?

This would likely cause the bug above.

We think you can workaround this bug by:

1. Deleting this section from your user settings.json
   or
2. Add this additional setting to your settings.json:

    "jupyter.experiments.optInto": [
        "CustomEditor"
    ],

[greazer]

One other question. @xcojonny, @takotab, do either of you have "Settings Sync" turned on (keep it off, if you've not ever turned it on).

[PeterMakus]

This shouldn't be happening but might be caused by this setting being in your user settings.json:

    "workbench.editorAssociations": [
        {
            "viewType": "jupyter.notebook.ipynb",
            "filenamePattern": "*.ipynb"
        }
    ],

Can you check if that editor association is there?

This would likely cause the bug above.

We think you can workaround this bug by:

1. Deleting this section from your user settings.json
   or

2. Add this additional setting to your settings.json:

    "jupyter.experiments.optInto": [
        "CustomEditor"
    ],

I experienced exactly the same issue and was able to circumvent the problem by following your instructions. Thanks!

[greazer]

@PeterMakus, good to hear! Did you happen to have "Settings Sync" turned on or know that you've ever turned it on? It's ok if you don't remember. Just looking for clues as to how these settings are getting messed up.

[PeterMakus]

No, that setting was turned off.

[xcojonny]

Hello,

@rchiodo: thanks a lot first!!! Deleting the section worked for me. Adding the section did not work!

@greazer: I'm using SettingsSync.

[warmbadetag]

Hi all,

I had this issue despite not having the editor association in settings.json

Adding the second section from @rchiodo's post resolved this issue, however.

[DonJayamanne]

@PeterMakus @xcojonny @warmbadetag
Are you using VS Code insiders or Stable?

[DonJayamanne]

@IanMatthewHuff I think the problem could be that users are falling into the custom editor experiment (now that its enabled) & they are also using insiders (this could be a serious issue for those using VS Code insiders if this is true & might require a point fix) or at some point tried native notebooks.

[PeterMakus]

@DonJayamanne I'm on the latest stable for ubuntu.

[claudiaregio]

@IanMatthewHuff I think the problem could be that users are falling into the custom editor experiment (now that its enabled) & they are also using insiders (this could be a serious issue for those using VS Code insiders if this is true & might require a point fix) or at some point tried native notebooks.

Experiment is for stable only

[DonJayamanne]

Tried this my self today (no issues), will be a tough one to validate.

[IanMatthewHuff]

@DonJayamanne Agreed. I tried turning custom editor on and off in stable and using native notebooks in insiders. I think at the bug bash I'll try manually adding in the custom editor association to my settings and seeing if it gets removed when I'm not in the experiment.

[biplavc]

This shouldn't be happening but might be caused by this setting being in your user settings.json:

    "workbench.editorAssociations": [
        {
            "viewType": "jupyter.notebook.ipynb",
            "filenamePattern": "*.ipynb"
        }
    ],

Can you check if that editor association is there?
This would likely cause the bug above.
We think you can workaround this bug by:

1. Deleting this section from your user settings.json
   or

2. Add this additional setting to your settings.json:

    "jupyter.experiments.optInto": [
        "CustomEditor"
    ],

I experienced exactly the same issue and was able to circumvent the problem by following your instructions. Thanks!

The first option of deleting the entry worked while the second option of adding the new entry didn't.

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.0-54-generic