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

Notebook fails to open #5268

Closed
diazdc opened this issue Mar 24, 2021 · 1 comment
Closed

Notebook fails to open #5268

diazdc opened this issue Mar 24, 2021 · 1 comment
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@diazdc
Copy link

diazdc commented Mar 24, 2021

Environment data

  • VS Code version: Version: 1.55.0-insider
    Commit: 469e4f6e2755b220dae3eccb04d1ddc587b84a5a
    Date: 2021-03-22T07:48:57.578Z
    Electron: 11.3.0
    Chrome: 87.0.4280.141
    Node.js: 12.18.3
    V8: 8.7.220.31-electron.0
    OS: Linux x64 5.8.0-45-generic

  • Jupyter Extension version: v2021.4.678042391

  • Python Extension version: v2021.4.677374727-dev

  • OS: Kubuntu 20.04

  • Python and/or Anaconda version: 3.8.5

  • Type of virtual environment used : Conda

  • Jupyter server running: Remote

Expected behaviour

Opening a jupyter notebook works.

Actual behaviour

I get the following error when opening a new or existing notebook (please see screenshots):

"Cannot open resource with notebook editor type 'jupyter-notebook', please check if you have the right extension installed or enabled."

Screenshot_20210324_130620

Screenshot_20210324_131233

Steps to reproduce:

Open a jupyter notebook, either new or existing.

(edit:) Downgraded to v2021.4.641214696 and notebooks open without any problem

@diazdc diazdc added the bug Issue identified by VS Code Team member as probable bug label Mar 24, 2021
@rchiodo
Copy link
Contributor

rchiodo commented Mar 24, 2021

If you upgrade VS code insiders to the latest release, this will go away.

Dupe of #5251

@rchiodo rchiodo closed this as completed Mar 24, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
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
Projects
None yet
Development

No branches or pull requests

2 participants