-
Notifications
You must be signed in to change notification settings - Fork 145
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
justMyCode stopped working after version 2024.10.0 #1785
Comments
I also got the same issue.
And I faced the same message "Frame skipped from debugging during step-in." like as @Real-Gecko commented: microsoft/vscode-python-debugger#139 (comment) |
This only seems to reproduce with test debugging. Not sure why at the moment. If you use this for debugging a file, stepping into 3rd party libraries works fine: {
"name": "Python Debugger: Current File",
"type": "debugpy",
"request": "launch",
"program": "${file}",
"purpose": ["debug-in-terminal"],
"console": "integratedTerminal",
"justMyCode": false,
"logToFile": true
}, But this won't (when debugging tests) {
"name": "Python: Debug Tests",
"type": "debugpy",
"request": "launch",
"program": "${file}",
"purpose": [
"debug-test"
],
"console": "integratedTerminal",
"justMyCode": false,
"logToFile": true
} The only difference I see in the launch is the 'rules' section of the launch args. "rules": [
{
"include": false,
"path": "c:\\Users\\rchiodo\\.vscode-insiders\\extensions\\ms-python.python-2024.23.2024121701-win32-x64\\python_files"
}
], The normal debug launch doesn't include those rules, the test debug launch does. I don't think that should be interfering though, but maybe there's a bug in the include matching. |
Here's the example test I used: import pytest
def test_debugstepinto():
pytest.approx(1.0, 1.2) # Try stepping into this line.
print("after") |
It also works for 3.11 or earlier. Must be a bug in the sys.monitoring code |
Found the location. We're not using the 'justMyCode' setting in the sys.monitoring to code to check if we should filter things not in the project scope. |
hi,
i'm using vs code with the python debugger extension and i noticed that recently stepping into 3rd party libraries stopped working. the version that i noticed this happening on is
2024.14.0
and the last version where i could get it to work is2024.10.0
which is the one that i currently switched to. can someone have a look into this?thanks
python version: 3.12.0
os version: windows 10 10.0.19045
vs code version: 1.96.0
current debugger version: 2024.14.0
last working version: 2024.10.0
launch.json config
The text was updated successfully, but these errors were encountered: