Limit no-config terminal env injection to shell integration to avoid relaunch warnings

[Copilot]

The debugger’s no-config terminal environment contribution was being applied at process-creation scope, so existing non-Python task terminals were flagged for relaunch and showed noisy warning indicators. This change scopes those mutations to shell integration so unrelated terminal sessions are no longer marked.

• Behavioral change

  • Update no-config env mutators to apply via shell integration (applyAtShellIntegration: true) instead of process creation.
  • Keeps debugpy <script.py> terminal flow intact while avoiding relaunch prompts on unrelated terminals.

• No-config env vars updated

  • PYDEVD_DISABLE_FILE_VALIDATION
  • VSCODE_DEBUGPY_ADAPTER_ENDPOINTS
  • BUNDLED_DEBUGPY_PATH
  • PATH append for noConfigScripts

• Unit test updates

  • Extend existing noConfigDebugInit unit assertions to verify mutator options are shell-integration based and not process-creation based.

const shellIntegrationMutatorOptions: EnvironmentVariableMutatorOptions = {
    applyAtShellIntegration: true,
};

collection.replace('VSCODE_DEBUGPY_ADAPTER_ENDPOINTS', tempFilePath, shellIntegrationMutatorOptions);
collection.append('PATH', `${pathSeparator}${noConfigScriptsDir}`, shellIntegrationMutatorOptions);

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• update.code.visualstudio.com
  • Triggering command: /usr/local/bin/node node ./out/test/runTest.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[rchiodo]

@copilot with this limiting, how does a user get the no config debug to work? What steps do they have to take?

[Copilot]

@copilot with this limiting, how does a user get the no config debug to work? What steps do they have to take?

No extra setup should be needed for normal use. No-config debug works in shell-integrated terminals (the default in VS Code): open a terminal and run debugpy <script.py> as before. The only caveat is existing terminals that were already open before the extension/environment update may need a one-time relaunch to pick up the new integration path; newly created terminals should work directly.

[rchiodo]

No extra setup should be needed for normal use. No-config debug works in shell-integrated terminals (the default in VS Code): open a terminal and run debugpy <script.py> as before. The only caveat is existing terminals that were already open before the extension/environment update may need a one-time relaunch to pick up the new integration path; newly created terminals should work directly.

@copilot then I'm not sure how this addresses the issue? Wouldn't that mean that the no config debug would still be applied in the example in the issue?

[Copilot]

No extra setup should be needed for normal use. No-config debug works in shell-integrated terminals (the default in VS Code): open a terminal and run debugpy <script.py> as before. The only caveat i...

Good catch — that command got truncated by markdown. The intended step is: open a shell-integrated terminal and run debugpy <script.py> (for example, debugpy app.py). If needed, create a new terminal first so shell integration env vars are present.