Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to debug tests when using zsh

See original GitHub issue

~Working on a PR for this~

Environment data

VS Code version: 1.44.0
Extension version (available under the Extensions sidebar): 2020.4.76186
OS and version: Ubuntu 18.04
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda, and virtualenv
Relevant/affected Python packages and their versions: unittest
Relevant/affected Python-related VS Code extensions and their versions: N/A
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): No
Value of the python.languageServer setting: Microsoft
Default shell: /bin/zsh

Expected behaviour

Expected to be able to debug tests.

Actual behaviour

Attempting to debug any tests runs this command to run the test with the debugger

 env DEBUGPY_LAUNCHER_PORT=33405 /home/carson/Documents/code/crystal/.env/bin/python /home/carson/.vscode/extensions/ms-python.python-2020.4.76186/pythonFiles/lib/python/debugpy/no_wheels/debugpy/launcher /home/carson/.vscode/extensions/ms-python.python-2020.4.76186/pythonFiles/visualstudio_py_testlauncher.py --us=./tests --up=test_*.py --uvInt=2 --result-port=43495

and results in the output:

zsh: no matches found: --up=test_*.py

with exit code 1

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

Use zsh as your default shell.
Attempt to debug any python unittest

Logs

Unnecessary

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

ShadowLNCcommented, Oct 12, 2021

I believe this also impacts the escaping of parentheses and quotes. I believe it is related to (potentially a duplicate of) #10398

1reaction

AAraKKecommented, Jun 15, 2020

I am so happy to see I am not the only one with this issue 😃 Is there any ETA? I have been ignoring this for months but now I cannot keep ignoring it since I really need to be able to debug individual tests.

Thanks!

Top Results From Across the Web

Known Issues - Warp Documentation

When you SSH, we start a Bash shell on the remote host. We built a wrapper around SSH to make Warp features possible....

How to debug this buggy variable assignment in zsh?

This is commonly used to update the prompt and the terminal title. It's likely that some of this code is buggy and modifying...

Error- XCodebuild - zsh: argument … | Apple Developer Forums

I'm using xcodebuild to build and test my project. ... xcodebuild[1960:35299] [MT] IDETestOperationsObserverDebug: 7.691 sec, +7.691 sec -- end zsh: ...

Running test until failure and viewing full debug: Bash not ...

However, not only does it only go through the loop once irrespective of the return value of the command (which is non-zero when...

Troubleshoot Terminal launch failures - Visual Studio Code

Troubleshooting steps · Test your shell directly. Try running your designated integrated terminal shell outside VS Code from an external terminal or command ......