Environment data

• VS Code version: 1.33.1
• Extension version (available under the Extensions sidebar): 2019.4.12954
• OS and version: RHEL 7.6
• Python version (& distribution if applicable, e.g. Anaconda): 3.7.2, miniconda 4.6.14
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Expected behaviour

Unit tests to discover

Actual behaviour

Python test log out put says:

MSI: wait: 0.1s and retry: 1

Steps to reproduce:

1. Set a bash environmental variable for http_proxy that is an authenticated proxy, either for user or in /etc/profile

Logs

Python Test Log Output:

MSI: wait: 0.1s and retry: 1
MSI: wait: 0.1s and retry: 2

Comments

This one puzzles me. I had been trying to use the new insiders remote extension, but the remote machine has an authenticated proxy that was stopping the python language server, and was forced to used jedi. (which still conflicts with gitlens from what I can tell.)

So, in order to get the remote to download the language server, I set the environmenal variable http_proxy per instructions, which worked. Insiders/remote downloaded the language server.

But now, on either the remote via ssh Insiders or running regular VS Code via RDC directly on the linux box, with the http_proxy set, unit tests won't discover - instead I get the error above. Removing the http_proxy variable from bash restores unit test discovery.