Skip to content

Debugger on VS Code is not working on Python with Output: DAP Server launched with command: conda run -n MyEnvironment --no-capture-output #885

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mmhammad opened this issue Apr 3, 2022 · 4 comments

Comments

@mmhammad
Copy link

mmhammad commented Apr 3, 2022

Environment data

  • debugpy version: 1.5.1
  • OS and version: Windows 10 Pro
  • Python version (& distribution if applicable, e.g. Anaconda): Python 3.9.7 | Anaconda Prompt (Miniconda3)
  • Using VS Code or Visual Studio: VS Code

Actual behavior

DAP Server launched with command: conda run -n testenv --no-capture-output --live-stream python c:\Users\user.name\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\lib\python\debugpy\adapter

Error
image

Expected behavior

It supposed to work normal and stop at the breakpoint.

Steps to reproduce:

I am using the Debugger on VS Code since a while for debugging Python scripts and it always worked fine. Yesterday I tried to work on some scripts written on C-Language and debugging them .. Now the Debugger on VS Code is not working on the Python scripts.

@cheTesta
Copy link

cheTesta commented Apr 4, 2022

Exact same situation here, debugger starts and stops with same error.

Error persist even when forcing update to debugpy==1.6.0

@fabioz
Copy link
Collaborator

fabioz commented Apr 4, 2022

I think there were some changes in the extension regarding running with conda in the latest version (and this appears related).

@karthiknadig should this be moved to vscode-python?

@fabioz
Copy link
Collaborator

fabioz commented Apr 4, 2022

Although it probably should be closed as it seems a duplicate of:

microsoft/vscode-python#18848
microsoft/vscode-python#18847

@mmhammad
Copy link
Author

mmhammad commented Apr 7, 2022

After trying several options, the problem was only solved by uninstalling VSCode completely and starting again from a new one.

@mmhammad mmhammad closed this as completed Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants