-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 on last release (2019.5) #5833
Comments
Also seeing this issue:
|
We are experiencing exactly the same issue. |
Me and my colleague seem to be having a similar issue. We get a Windows popup saying "Timeout waiting for debugger connection". The terminal reads (user paths edited etc.):
Reverting to the previous version (from 2019.5.17059 to 2019.4.12954) fixes the issue. |
We're working on getting a point release out ASAP. Apologies for the inconvenience caused. |
After the last update, some parts of the debugger stop working. The setup is not simple, with multiple folders in the workspace, specific CWD in lauch.json, but it runs fine until version 2019.4.12954, but broke on update to 2019.5.17059.
I will try to give further details, like a minimal reproducible example, but due time constraints I'll give the minimum to report the bug.
Environment data
VS Code version:
Version: 1.34.0
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:55:35.507Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 5.0.16-300.fc30.x86_64
Extension version:
[BROKEN VERSION]
Name: Python
Id: ms-python.python
Description: Linting, Debugging (multi-threaded, remote), Intellisense, code formatting, refactoring, unit tests, snippets, and more.
Version: 2019.5.17059
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-python.python
[LATEST WORKING VERSION]
Version: 2019.4.12954
OS and version: GNU/Linux Fedora 30 64bit
Python version: Python 3.7.3
Expected behaviour x Actual behaviour
After the upgrade, the debugger is somehow broken. Roughly, the CWD or source code mapping is trying the wrong path. The debugger starts, but when you try to set a breakpoint, it shows up in the console:
pydev debugger: warning: trying to add breakpoint to file that does not exist: /home/user/work/company/project/back-end/project/back-end/app.py (will have no effect)
The correct path would be
/home/user/work/company/project/back-end/app.py
. Also, if you set up a breakpoint in a line before the debugger starts, it does not break on it when running.My workspace have multiple folders, and my configuration on laucher sets CWD. I tried to adapt the launcher.json config to work on the new version, like removing the
cwd
in the laucher setting. It fixed this issue, but broke other stuff.I tried this with fresh settings, and with all extensions disabled except the Python one.
Some parts (the relevant ones) of my workspace settings file. The file is in
root_workspace/misc/project.code-workspace
. More on the files tree above.My
.vscode/launch.json
file (relevant parts):PS: I renamed some names like my username or project name.
Also, if it can help, the redacted file tree of the project. I remove irrelevant parts. Generated by
$ tree
.Logs
Output for
Python
in theOutput
panelThe text was updated successfully, but these errors were encountered: