Skip to content

Remote SSH cannot find Python Interpreter if conda takes too long #17569

Description

@blattier

May be similar to #16286 where a future python update resolved the issue, but wanted to expedite an update if required.

Environment data

  • VS Code version: 1.60.2
  • Extension version (available under the Extensions sidebar): Jupyter v2021.8.2041215044, Python v2021.9.1246542782
  • OS and version: MacOS Big Sur 11.3.1
  • Python version (& distribution if applicable, e.g. Anaconda): Local: Python 3.5.2 64-bit, Remote SSH: Python 3.7.3 64-bit
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda in Remote SSH
  • Relevant/affected Python packages and their versions: N/A
  • Relevant/affected Python-related VS Code extensions and their versions: Pylance v2021.9.3
  • Value of the python.languageServer setting: Pylance

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

We have already switched to pylance

Expected behavior

Until September 27, 2021, when we use remote SSH on VS code to connect to a workspace on our AWS GPU, we could select the Python interpreter that is installed on the GPU. We have 2 Python 3.7.3 64 bit python interpreters available to us provided we remote SSH into a GPU workspace in VS code -

image

Actual behavior

As of September 27, 2021, the only python interpreters that I can select when I remote SSH into the GPU are the ones that are installed locally on my computer. These are obviously incorrect as they do not match Anaconda python versions installed on the GPU. We have even tried updating .vscode/settings.json value for python.pythonPath with the exact directory of the python interpreter location, but the remote SSH workspace can no longer see the correct python interpreters.

  • When clicking on "Python: Select Interpreter" from the command pallet nothing happens.
  • When attempting to select the correct Kernel when creating a new blank workbook with Jupyter I am only prompted with my local python options, neither of the GPU options are available.

image

Without these python options on the gpu, I'm not able to develop using the packages we have created.

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

Step 1 -- Remote into GPU vis SSH
image

Step 2 -- Open command pallet and click on "Python: Select Interpreter"

  • Actual behavior for me here is for nothing to happen when clicking that

Step 3 -- Open command pallet and click on "Jupyter: Create New Blank Notebook"
image

Step 4 -- Click "Select Kernel"

  • only local python options available, nothing from GPU

image

Metadata

Metadata

Assignees

Labels

area-environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bug

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions