Skip to content
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

Debugger Broken | v2021.12.1559732655 #18453

Closed
drcrook1 opened this issue Feb 5, 2022 · 14 comments
Closed

Debugger Broken | v2021.12.1559732655 #18453

drcrook1 opened this issue Feb 5, 2022 · 14 comments

Comments

@drcrook1
Copy link

drcrook1 commented Feb 5, 2022

Launch.json

{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Module",
"type": "python",
"request": "launch",
"module": "app.run",
"console": "integratedTerminal"
}
]
}

Simple module run that ends up spinning up a Flask server on port 80 I need to debug. Was working great in the prior version, v2021.12.1559732655.

The latest version v2022.0.1786462952 looks like it tries to spin up debugging, but it quite simply just goes away almost immediately. I'm on the latest Windows 11. Just to clarify one more time, the prior version works fine.

Prior version when hitting F-5 moves you to a terminal and starts the server. The new version doesn't do anything at all.

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Feb 5, 2022
@WeianMao
Copy link

WeianMao commented Feb 5, 2022

I am not sure whether your issue is the same with me. my issue is when i debug a python file on remote server(with conda env), the debugger exit with no any reason. is it the same with you?

@shanshuo
Copy link

shanshuo commented Feb 5, 2022

I am not sure whether your issue is the same with me. my issue is when i debug a python file on remote server(with conda env), the debugger exit with no any reason. is it the same with you?

I have the same issue. I downgrade the Python Extention to v2021.12.1559732655 and solved the issue. Maybe it's a bug of v2021.12.1559732655.

@sfaroy
Copy link

sfaroy commented Feb 5, 2022

Same issue here. Spent hours on this. The thing is that there is also no clue for the crash in any of the log windows

@cameronshinn
Copy link

I am having this issue as well

@hank3df
Copy link

hank3df commented Feb 7, 2022

same issue , downgrade the Python extension to v2021.12.1559732655 works.

@CranBarry
Copy link

same issue on v2022.0.1786462952 , debug not working, with no error log, and Python Debug Console didn't show.
Downgrade the Python extension to v2021.12.1559732655 then works.

@rareal
Copy link

rareal commented Feb 7, 2022

same problem here, downgrading to v2021.12.1559732655 works as well.

While this is not fixed, is there a way to specify v2021.12.1559732655 in remote.SSH.defaultExtensions?

@xujing113221
Copy link

same, i can't debug python on v2022.0.1786462952. but who can tell me how to downgrade the version?

@rareal
Copy link

rareal commented Feb 7, 2022

same, i can't debug python on v2022.0.1786462952. but who can tell me how to downgrade the version?

go the extension page > down arrow next to Uninstall > install another version

@xujing113221
Copy link

same, i can't debug python on v2022.0.1786462952. but who can tell me how to downgrade the version?

go the extension page > down arrow next to Uninstall > install another version

thanks, it works.

@LukasFehring
Copy link

unfortunately i have the same issue :) Fortunately i allready knew about downgrading :)

If one tries to debug a unittest it just runs forever

@gcheron
Copy link

gcheron commented Feb 7, 2022

same issue here, a downgrade solved the problem!

@Alexey-Kamenev
Copy link

I'm having the same problem as well. In my case I'm debugging the code inside a Docker container. What I've found so far is this:

  • Downgrading to a previous version (v2021.12.1559732655) makes debugging work as expected.
  • I can make the latest (broken) version of the extension work if I change remoteUser to root in VS Code remote container config file.
  • Finally, this issue seems to affect only Python 3 (and corresponding conda distros) but not Py2 - it seems to work in my case even with non-root container user.

@karthiknadig
Copy link
Member

Duplicate of #18436

@karthiknadig karthiknadig marked this as a duplicate of #18436 Feb 7, 2022
@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Feb 10, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests