FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Limit no-config terminal env injection to shell integration to avoid relaunch warnings by Copilot · Pull Request #1038 · microsoft/vscode-python-debugger · GitHub

/ vscode-python-debugger Public

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

Draft
Rich Chiodo (rchiodo) with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-python-debugger-warnings
ConversationCommits (2)ChecksFiles changed
Draft

Limit no-config terminal env injection to shell integration to avoid relaunch warnings#1038
Rich Chiodo (rchiodo) with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-python-debugger-warnings

Conversation

Copilot AI commented May 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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:

Copilot AI linked an issue May 15, 2026 that may be closed by this pull request
python debugger is adding warnings to unrelated terminal sessions #1037
Open
Copilot AI changed the title [WIP] Fix python debugger adding warnings to unrelated terminal sessions Limit no-config terminal env injection to shell integration to avoid relaunch warnings May 15, 2026
Copilot AI requested a review from Rich Chiodo (rchiodo) May 15, 2026 20:39

Rich Chiodo (rchiodo) commented May 15, 2026

Copy link
Copy Markdown
Contributor

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

Copilot AI commented May 15, 2026

Copy link
Copy Markdown
Contributor Author

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.

Rich Chiodo (rchiodo) commented May 15, 2026

Copy link
Copy Markdown
Contributor

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 AI commented May 15, 2026

Copy link
Copy Markdown
Contributor Author

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.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Rich Chiodo (rchiodo) Awaiting requested review from rchiodo

At least 1 approving review is required to merge this pull request.

Assignees

Rich Chiodo (rchiodo)

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

python debugger is adding warnings to unrelated terminal sessions

2 participants

Back | FazBrowse Home | New Git URL