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..

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:

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

Logs

User belongs to experiment group 'jupyterTest'

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 24 (10 by maintainers)

Commits related to this issue

Auto-update VSCode editor associations for Jupyter br3ndonland/dotfiles@027531e microsoft/vscode-jupyter#3988 https://github.com/microsoft/vscode-jupyter/releases/tag/2020.11.2 https://github.com/mi... — committed to br3ndonland/dotfiles by br3ndonland 3 years ago
Auto-update VSCode editor associations for Jupyter br3ndonland/dotfiles@027531e microsoft/vscode-jupyter#3988 https://github.com/microsoft/vscode-jupyter/releases/tag/2020.11.2 https://github.com/mi... — committed to br3ndonland/dotfiles by br3ndonland 3 years ago

Most upvoted comments

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:

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

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

+19

rchiodo on Nov 21, 2020

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!

PeterMakus on Nov 21, 2020

@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

claudiaregio on Nov 23, 2020

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

PeterMakus on Nov 23, 2020