Skip to content

Shell integration not injected for debug terminals in remote environments #1337

@renan-r-santos

Description

@renan-r-santos

When using the shellStartup activation type in a remote VS Code environment, the Python environment isn't activated in the terminal where the debugger is launched. This affects all environments that need to be activated, like Conda and Pixi.

The issue only happens when all three conditions are met:

  1. Remote environment
  2. shellStartup activation type
  3. Launching the debugger (integrated terminal)

Opening a regular terminal in the same remote environment works fine. Debugging locally also works fine. Setting autoActivationType to command works around the issue.

There is a fix waiting for review over here microsoft/vscode#300428.

Metadata

Metadata

Assignees

Labels

area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.bugIssue identified by VS Code Team member as probable bug

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions