Jupyter notebook not shown on screen

OS/Web Information

• Web Browser: Firefox 93.0
• Local OS: Ubuntu 21.04
• Remote OS: same (running locally)
• Remote Architecture: Installed anaconda (conda version 4.10.3)
• code-server --version: 3.12.0

Steps to Reproduce

1. Open an existing notebook
2. The file kind of opens, meaning the contents are not shown, the wait indicator is running but the outline can be shown. It can be run as well but does not recognize the installed python interpreter (ms-python) or jupyter notebook (ms-toolsai). It asks again and again to install a python interpreter.
3. New markdowns can be added, show up in the outline (without text) but not on the screen.
4. The same happens when creating a new notebook
5. Notebooks can be normally created, opened and run in local vscode (1.61.1)
6. code-server has been removed and installed again to see if anything differed. That was not the case.

Python code runs as expected.

Expected

When opening an existing notebook, it shows the notebook on the screen that can be run using F5. Also it should be aware of already existing installed python environments.

I would like to see a jupyter notebook and be able to run the cells like in the local version.

Actual

Nothing.

Logs

Log files are added. There is no log activity to be seen on the screen (code-server.log) when I try to open and run a jupyter notebook.

Screenshot

Has been added. The editor shows a blank screen but the outline shows that a lot is present. The sidebar is identical as that of local vscode.

Notes

This issue can be reproduced in VS Code: No

code-server.log exthost.log remoteagent.log telemetry.log

[code-asher]

You might need to download an older version of the extension.

An example of switching to OpenVSX can be found here: https://github.com/cdr/code-server/blob/v3.12.0/docs/FAQ.md#how-do-i-use-my-own-extensions-marketplace

The next release of code-server will likely use OpenVSX by default.

[code-asher]

Seems likely related to our recent extension issues in our marketplace in which case it would be fixed by our switch to Open VSX https://github.com/cdr/code-server/pull/4319.

Workarounds are to install the .vsix or switch to Open VSX early.