Vscode 1.104 Testing Panel does not see the $PATH anymore

[alanwilter]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.104
• OS Version: macOS Sequoia 15.6.1 (24G90)

I have a python project whose pytest works fine in Vscode Testing panel. My integration test depends on a binary (typst, installed via homebrew).

With the new Vscode 1.104 this is broken, it does not see the $PATH and does not find typst.

[eleanorjboyd]

Few questions:

• are you running test or debugging tests?
• do you have the python environments extension installed?
• how are you added it to the $PATH var?

[alanwilter]

I'm using Run Test. But Debug Test and Run Test with Coverage fail the same way.

I have Python Environments extension. With or without it, the issue is there.

I work on a Mac and I use homebrew. I don't do anything special for the $PATH, never needed. If I run pytest in my vscode terminal, the integration tests passed fine, no wonder, since which typst is in the $PATH.

But something happened in Vscode v1.104 and when I run the Testing via GUI it fails.

FYI, I circumvented this development issue by embedding the binary in my python package. But the issue is there, and with v1.103 it was not.

[eleanorjboyd]

Hi! Sorry on the delay here- are you still facing this issue?

[alanwilter]

The answer is yes and no.

You can use Vscode debug mode to peek r1.stdout:

def test_system() -> None:
    r1 = run(["sh", "-c", "echo $PATH"], capture_output=True, text=True)
    assert r1.returncode == 0

And then you'll see that, for Mac users with homebrew, /opt/homebrew/bin/ is not there. But the python env is, e.g. .pyenv/versions/3.12.11/envs/mbpdfgen/bin.

Perhaps it's just a matter of configuration, but I frankly don't know where to add e.g. /opt/homebrew/bin/.

[eleanorjboyd]

Looping in @anthonykim1 - Potential Interaction with Activation Hooks Change

Issue: Tests run via the Testing Panel on macOS are missing /opt/homebrew/bin and other system paths from their PATH environment variable (only showing /usr/bin:/bin:/usr/sbin:/sbin - 29 chars vs expected ~500+ chars). Tests work fine when run in the integrated terminal.

idea of cause?

The Extension Host process starts with a truncated PATH (just /usr/bin:/bin:/usr/sbin:/sbin). Previously (1.103), activation happened via shell profile modification which may have ensured the full PATH was available. Now with shell integration scripts (1.104), there may be a timing issue where:

1. Tests start running via runInBackground (Python Envs extension path)
2. Extension Host hasn't completed shell integration yet
3. Tests get the truncated Extension Host PATH instead of the full shell PATH

Diagnostic logging shows:

• Extension Host process.env.PATH: 29 chars (truncated)
• User's actual shell PATH: ~500+ chars (includes /opt/homebrew/bin)
• The PATH is already truncated when we first access it in our activation code

I could (on the testing side) explicitly query the user's login shell to get the full PATH in activation/service.ts. But this doesn't feel like the best option. What are your thoughts @anthonykim1? What is the expected experience here?