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

Interactive window is using the wrong env for activation for remote development #16064

Open
shashankvidiyalaC3 opened this issue Sep 19, 2024 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug interactive-window Impacts interactive window triage-needed Issue needs to be triaged

Comments

@shashankvidiyalaC3
Copy link

shashankvidiyalaC3 commented Sep 19, 2024

Environment data

  • VS Code version: 1.92.1
  • Jupyter Extension version (available under the Extensions sidebar): v2024.8.1
  • Python Extension version (available under the Extensions sidebar): v2024.14.1
  • OS (Windows | Mac | Linux distro) and version: Local machine mac -osx, remote machine fedora

Expected behaviour

It should use the env for the remote machine to start the interactive windows

Actual behaviour

Interactive window doesn't open at all, and the extension is attempting to use env of my local machine

Steps to reproduce:

  1. Use a local osx machine and try to ssh to a remote vscode on linux
  2. Try to use interactive window

Logs

}
2024-09-19 21:59:25.458 [error] [
  'Failed to activate a workspace, Class name = v, completed in 710ms, has a falsy return value, Arg 1: <Uri:Untitled-1.ipynb>, Arg 2: {"started":1726783164620}, Return Value: undefined',
  l [Error]: Failed to resolve env "/usr/local/share/c3/v8/conda/Miniconda3-py39_23.1.0-1-MacOSX-x86_64"
      at ae (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2041224)
      at oe (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2039184)
      at Immediate.<anonymous> (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2035478)
      at processImmediate (node:internal/timers:478:21) {
    code: -4,
    data: undefined
  }
]
2024-09-19 21:59:25.458 [error] Failure during activation. l [Error]: Failed to resolve env "/usr/local/share/c3/v8/conda/Miniconda3-py39_23.1.0-1-MacOSX-x86_64"
    at ae (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2041224)
    at oe (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2039184)
    at Immediate.<anonymous> (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2035478)
    at processImmediate (node:internal/timers:478:21) {
  code: -4,
  data: undefined
}
2024-09-19 21:59:25.458 [error] sendStartupTelemetry() failed. l [Error]: Failed to resolve env "/usr/local/share/c3/v8/conda/Miniconda3-py39_23.1.0-1-MacOSX-x86_64"
    at ae (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2041224)
    at oe (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2039184)
    at Immediate.<anonymous> (/home/c3/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/out/client/extension.js:2:2035478)
    at processImmediate (node:internal/timers:478:21) {
  code: -4,
  data: undefined

@shashankvidiyalaC3 shashankvidiyalaC3 added the bug Issue identified by VS Code Team member as probable bug label Sep 19, 2024
@vs-code-engineering vs-code-engineering bot added the triage-needed Issue needs to be triaged label Sep 19, 2024
@amunger
Copy link
Contributor

amunger commented Sep 20, 2024

can you try running Python: Select Interpreter to select the env you want to use first

@amunger amunger added the info-needed Issue requires more information from poster label Sep 20, 2024
@shashankvidiyalaC3
Copy link
Author

Thanks running Python: Select Interpreter and creating a new venv fixed my issue

@amunger amunger closed this as completed Sep 20, 2024
@shashankvidiyalaC3
Copy link
Author

If activating the interpreter fails can we show some error message to perform this action ?

@amunger amunger reopened this Sep 20, 2024
@amunger amunger added interactive-window Impacts interactive window and removed info-needed Issue requires more information from poster labels Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug interactive-window Impacts interactive window triage-needed Issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants