Stuck at discovering Python Interpreters in ssh connection

[L-WWEEII]

VS Code version
Version: 1.74.2

Extension version
v2022.20.1
Python(Pylance etc.)

OS type
Win10

Python distribution
Miniconda(in remote ssh)

Python version
3.8

Language server
Default

Expected behaviour
Be able to find the Python interpreter instead of discovering it all the time！

Actual behaviour

Stuck at discovering Python Interpreters forever

I have installed Python extensions on remote server A, and when I open a Python file on the remote server, it says "discovering Python interpreter" at the bottom of the interface, but it never goes away. But when I install the extension on another remote server B, I don't have this problem. How can I fix this problem on server A?

Steps to reproduce
Open any python related file(notebook, .py) it will start to discover and stuck there.

Logs
LSP Notebooks experiment is enabled
LSP Notebooks interactive window support is enabled

conda info --json
python -c "import sys;print(sys.executable)"
/usr/bin/python ./.vscode-server/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ./.vscode-server/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
/usr/bin/python3 ./.vscode-server/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ./.vscode-server/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
[ERROR 2023-0-10 6:33:10.26]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:10.104]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:10.123]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:10.139]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:10.166]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:10.179]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:20.416]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:22.63]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
[ERROR 2023-0-10 6:33:45.214]: Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.

Code of Conduct
I agree to follow this project's Code of Conduct

[karrtikr]

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority. Thanks for understanding and the patience!

[karrtikr]

Please provide the logs as mentioned in the issue template. Set python.logging.level to debug in User settings, reload window, then perform the steps to reproduce before providing the logs.

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

[GerardMaggiolino]

I have the same issue. VS Code is 1.75.0, Mac ARM download. Running through ssh remotely on an Ubuntu 20.04 server, extension 2023.2.10, have tried pre-release as well.

Selecting the interpreter does not stop interpreter discovery. Additionally, it seems like none of the basic functionality is working - right clicking doesn't prompt to "Go to definition / references", instead displaying the standard "change all occurrences".

Have uninstalled / reinstalled removing all cached files, both locally and in ~/.vscode-server, have tried universal and ARM build. Extension logs from startup + selecting an interpreter:

2023-02-02 21:14:51.629 [info] Extension host with pid 1974899 started
2023-02-02 21:14:51.631 [error] Error: EEXIST: file already exists, open '/home/gmaggiolino/.vscode-server/data/User/workspaceStorage/542e81e8020bc7bd6926b910f095d44e/vscode.lock'
2023-02-02 21:14:51.636 [info] Lock '/home/gmaggiolino/.vscode-server/data/User/workspaceStorage/542e81e8020bc7bd6926b910f095d44e/vscode.lock': Could not acquire lock, checking if the file is stale.
2023-02-02 21:14:51.640 [info] Lock '/home/gmaggiolino/.vscode-server/data/User/workspaceStorage/542e81e8020bc7bd6926b910f095d44e/vscode.lock': The lock looks stale, waiting for 2s.
2023-02-02 21:14:51.773 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2023-02-02 21:14:51.776 [info] ExtensionService#_doActivateExtension ms-python.python, startup: false, activationEvent: 'onLanguage:python', root cause: ms-python.isort
2023-02-02 21:14:51.810 [info] ExtensionService#_doActivateExtension ms-toolsai.jupyter, startup: false, activationEvent: 'onLanguage:python'
2023-02-02 21:14:51.817 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2023-02-02 21:14:53.649 [info] Lock '/home/gmaggiolino/.vscode-server/data/User/workspaceStorage/542e81e8020bc7bd6926b910f095d44e/vscode.lock': The lock looks stale even after waiting for 2s.
2023-02-02 21:14:53.655 [info] Lock '/home/gmaggiolino/.vscode-server/data/User/workspaceStorage/542e81e8020bc7bd6926b910f095d44e/vscode.lock': Deleting a stale lock.
2023-02-02 21:14:53.690 [info] Lock '/home/gmaggiolino/.vscode-server/data/User/workspaceStorage/542e81e8020bc7bd6926b910f095d44e/vscode.lock': Lock acquired.
2023-02-02 21:14:54.147 [info] ExtensionService#_doActivateExtension ms-toolsai.jupyter-renderers, startup: false, activationEvent: 'api', root cause: ms-toolsai.jupyter
2023-02-02 21:14:54.217 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2023-02-02 21:14:54.243 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2023-02-02 21:14:54.877 [info] ExtensionService#_doActivateExtension ms-python.isort, startup: false, activationEvent: 'onLanguage:python'
2023-02-02 21:14:54.878 [info] ExtensionService#_doActivateExtension ms-python.vscode-pylance, startup: false, activationEvent: 'onLanguage:python'
2023-02-02 21:14:55.585 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-02-02 21:14:55.586 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-02-02 21:14:55.586 [info] Eager extensions activated
2023-02-02 21:15:48.669 [error] Error: write after end
	at new NodeError (node:internal/errors:371:5)
	at _write (node:internal/streams/writable:319:11)
	at Socket.Writable.write (node:internal/streams/writable:334:10)
	at /home/gmaggiolino/.vscode-server/extensions/ms-python.isort-2022.8.0/dist/extension.js:1:127453
	at new Promise (<anonymous>)
	at u.write (/home/gmaggiolino/.vscode-server/extensions/ms-python.isort-2022.8.0/dist/extension.js:1:127371)
	at m.doWrite (/home/gmaggiolino/.vscode-server/extensions/ms-python.isort-2022.8.0/dist/extension.js:1:116975)
	at /home/gmaggiolino/.vscode-server/extensions/ms-python.isort-2022.8.0/dist/extension.js:1:116870
	at runNextTicks (node:internal/process/task_queues:61:5)
	at processImmediate (node:internal/timers:437:9)

[karrtikr]

@GerardMaggiolino Please provide #20485 (comment).

[triostones]

I have a similar problem with vscode-pull-request-github. Downgrading vscode-pull-request-github to v0.56 solved my problem.

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.