Cannot get Pyright nor Pyrefly working with code-server.

[JacekHoleczek]

I am trying to play with the code-server on a Ubuntu 22.04 / x86_64 machine (Python 3.10.12).

I tried three recent versions: "v4.108.2", "v4.107.1", and "v4.106.3".

I manually install/unpack the code-server-*-linux-amd64.tar.gz file and run it using the ~/.../code-server-*-linux-amd64/bin/code-server command.

For each version, I always start with a "clean" environment:

rm -rf ~/.local/share/code-server/ ~/.config/code-server/ ~/.cache/Microsoft/ ~/.cache/pip/ ~/.ipython/ ~/.jupyter/ ~/.local/share/jupyter/ ~/.cache/jedi/

I connect to the server using Firefox (a "new private window").

I install the "Python (ms-python)", "Jupyter (ms-toolsai)", "Pyright (ms-pyright)", and "Pyrefly - Python Language Tooling (meta)" extensions.

I can then selectively "Disable" and "Enable" the "Pyright" and "Pyrefly".

When I open a ".ipynb" file ...

... "Pyright" never works ...

... "Pyrefly" works only with "v4.106.3".

No warnings or errors are reported in the code-server's console.

The command "Python: Restart Language Server" results in an error "command 'python.analysis.restartLanguageServer' not found".
This is a problem when I need to change the kernel to another "Python Environment" (the LSP server should "switch" to a different set of Python packages available in the new "virtual environment").

What am I possibly missing?

[code-asher]

I would try https://github.com/detachhead/basedpyright instead.

From what I understand, Pyright is proprietary and only works on proprietary VS Code (not open source VS Code which code-server is based on).

[JacekHoleczek]

In a (standalone) "JupyterLab", I've recently tried "Pyright" and "Basedpyright". Both could be installed (without problems) and worked, but "Pyright" behaved better.
Then I found "Pyrefly" to be even better.

In a "code-server v4.108.2", I now installed the "Basedpyright v1.37.2 VSIX" and it starts fine. However, when I open a ".ipynb" file and select/change the kernel to some "Python Environment", it does not "switch" to the different set of Python packages available in the new "virtual environment" (hence the LSP mainly shows "Import ... could not be resoved", "Type of ... is unknown", and so on, but the "Run All" works fine, of course).