Testing code lenses don't show for remote sessions to a directory symlink.

[yphillip]

Environment data

• VS Code version: 1.38.1
• Extension version: 2019.9.34911
• OS and version: WSL (Windows 10.0.18362 Build 18362)
• Python version: Conda 3.7.4
• Type of virtual environment used: Conda
• Relevant/affected Python packages and their versions: pytest-5.0.1

Expected behaviour

I am using python in a conda environment in WSL. I configured VS Code to use the correct WSL python interpreter, and I expected that the code adornments would be available.

Actual behaviour

VSCode discovers the test and it can be run , but there is no visible adornment.

WSL (no code adornments):

Interestingly, I installed conda/python on Windows, and when I switch over to that interpreter in VS Code, the code adornments are available.

Windows (code adornments available)

Steps to reproduce:

1. Install pytest.
2. Write a test
3. Choose the WSL Conda python interpreter
4. Code adornments not available.
   vs.
5. Disconnect from WSL
6. Choose the Windows Conda python interpreter
7. Code adornments become available

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

> ~/miniconda3/envs/APT/bin/python ~/.vscode-server/extensions/ms-python.python-2019.9.34911/pythonFiles/testing_tools/run_adapter.py discover pytest -- -s .
cwd: ~/PhillipYen/Desktop/project1
> conda info --json
> ~/miniconda3/envs/APT/bin/python ~/.vscode-server/extensions/ms-python.python-2019.9.34911/pythonFiles/testing_tools/run_adapter.py discover pytest -- -s --cache-clear .
cwd: ~/PhillipYen/Desktop/project1

[yphillip]

Hi Don, To be more explicit, I do the following: 1. Open Windows Terminal to start WSL, 2. conda activate APT (to go into my the conda environment) 3. cd to the project folder 4. enter "code ." to start VSCode I also have the Remote - WSL v0.39.5 Extension installed. Is what you mean when you say open VSCode inside WSL? Thanks, Phil

…

On Tue, Sep 17, 2019 at 12:35 PM Don Jayamanne ***@***.***> wrote: Choose the WSL Conda python interpreter Please note, if using wsl you'll need to open VSCode inside wsl using the remote extension in VSCode. i.e.wsl is supported (by then python extension) only when VSCode is launched inside wsl using remote extensions. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7443?email_source=notifications&email_token=AB4B6XWHNXPAMQGX3YFXV5LQKEWOVA5CNFSM4IXUGMY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65U57A#issuecomment-532369148>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4B6XS56E7NW2APUIFL2UTQKEWOVANCNFSM4IXUGMYQ> .

[yphillip]

My colleague showed me another way to start VS Code with WSL, and in this way, the code adornments become available:

1. Open VS Code in Windows (e.g through Start menu)
2. Click "Open a remote window" in the bottom left hand corner
3. Click "Remote-WSL: New Window"
4. In the new VS Code window, browse to your project folder.
5. Make sure the interpreter is correct.
6. Code adornments should now be available.

Still unsure why this method works for showing the adornments, but the code . from the WSL Windows Terminal method doesn't work.

[yphillip]

I think I figured it out. The problem has something to do with running code . from a directory derived from a symbolic link.

When I cd to the absolute path and then run code . , the code adornments become available.
cd
Before, I had cd'ed to the path via a symbolic link and then run code ., which wouldn't show the code adornments.

[ericsnowcurrently]

Thanks for letting us know about this, @yphillip. I was able to reproduce the problem via both remote-WSL and remote-SSH (to a linux host). I was not able to reproduce this with "code ." directly on linux. We will investigate further.

Repro

To reproduce:

1. run mkdir /tmp/test-7443
2. run ln -s /tmp/test-7443 /tmp/test-7443-lnk
3. create /tmp/test-7443/test_spam.py with content of def test_spam(): assert True
4. open /tmp/test-7443-lnk in VS Code (on WSL: code /tmp/test-7443-lnk; over SSH: use UI)
5. open test_spam.py
6. in the command palette, run the command to configure tests (pytest)

Via remote-WSL or remote-SSH, the code lens for the test does not show up. (Note that the test does show up in the test explorer on the left.) Both remote sessions work correctly if /tmp/test-7443 is opened directly (rather than the symlink).

[ericsnowcurrently]

Note that this may also be a problem with upstream VS Code, rather than the extension. We'll figure that out.

[sammo]

Same issue here. No adornments for pytest. I'm using vscode on mac Mojave and a python 3.7.3 conda environment.

[BoPeng]

Same here, I do not know what is WSL ad I do not have any symbolic link in the path. I am in conda python 3.8 environment under mac catalina.

Edit: I really do not know what happened, these Run Test adornments suddenly appeared.

[brettcannon]

In our upcoming test provider we won't have codelenses, but there will be gutter icons which do work under e.g. WSL.