debupy ignores justMyCode == False when used in listen mode

[TommasoBendinelli]

I have set up .vscode/launch.json as this:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python Debugger: Current File",
            "type": "debugpy",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": false,
        },
        {
                    "name": "Attach",
                    "type": "debugpy",
                    "request": "attach",
                    "pathMappings": [
                        {
                            "localRoot": "${workspaceFolder}",
                            "remoteRoot": "."
                        },
                        {
                            "localRoot": "/home/tommaso/repos/myrepo/xxx/lib/python3.11/site-packages",
                            "remoteRoot": "/home/tommaso/repos/myrepo/xxx/lib/python3.11/site-packages"
                        }
                    ],
                    "connect": {
                        "port": 55678
                    },
                    "subProcess": true,
                    "justMyCode": false,
                }]

}

Furthermore I have also set up settings.json as this:
{
"jupyter.debugJustMyCode": false,
"debug.disassemblyView.showSourceCode": true,
"debugpy.debugJustMyCode": false
}

Environment data

• debugpy version: debugpy-1.8.12
• OS and version: PtvsdWheels37 - experiment breaks the debugger under windows debugpy#140~20.04.1-Ubuntu)
• Python version (& distribution if applicable, e.g. Anaconda): 3.11.5
• Using VS Code or Visual Studio: VSCODE

Actual behavior

Frame skipped from debugging during step-in.
Note: may have been skipped because of "justMyCode" option (default == true). Try setting "justMyCode": false in the debug configuration (e.g., launch.json).

Expected behavior

I should be able to step in library code.
def main():
import debugpy
debugpy.listen(("localhost", 55678))

# LibraryCode you want to step in

[rchiodo]

Thanks for the issue. I can reproduce this with latest debugger extension in VS code. It seems it's using an auto-generated configuration for attach and not using the launch.json for attach.

I can see it in the attach request:

D+00000.890: Client[1] --> {
                 "seq": 2,
                 "type": "request",
                 "command": "attach",
                 "arguments": {
                     "type": "python",
                     "request": "attach",
                     "name": "Attach to Python",
                     "connect": {
                         "port": 5679,
                         "host": "localhost"
                     },
                     "clientOS": "windows",
                     "debugOptions": [
                         "RedirectOutput",
                         "ShowReturnValue"
                     ],
                     "showReturnValue": true,
                     "workspaceFolder": "c:\\Users\\rchiodo\\source\\testing\\test_pylance",
                     "__sessionId": "fc609b5e-0dcc-43bf-9b9a-c67374324487"
                 }
             }

If I go back to 2024.14.0, this problem no longer occurs and I can use my own launch.json for the attach and set the justMyCode setting.

Attach request looks like this instead then:

D+00005.531: Client[1] --> {
                 "seq": 2,
                 "type": "request",
                 "command": "attach",
                 "arguments": {
                     "name": "Python Debugger: Attach to listening debugpy",
                     "type": "debugpy",
                     "request": "attach",
                     "connect": {
                         "port": 5679
                     },
                     "justMyCode": false,
                     "logToFile": true,
                     "__configurationTarget": 6,
                     "clientOS": "windows",
                     "debugOptions": [
                         "RedirectOutput",
                         "ShowReturnValue"
                     ],
                     "showReturnValue": true,
                     "workspaceFolder": "c:\\Users\\rchiodo\\source\\testing\\test_pylance",
                     "__sessionId": "89c7b48f-f06f-4300-ab07-c6d162c74f25"
                 }
             }

Transferring to the debugger extension for VS code.

[eleanorjboyd]

will investigate thank you

[eleanorjboyd]

Hi! I am trying this but not seeing the bug. What machine type do you both have? Are these steps correct:

1. copied launch.json included in original issue filing
2. had this script

import pytest

if __name__ == "__main__":
    pytest.main()
    print("This is a test")

3. ran it using the "run and debug" menu with the "python debugger: current file" selected

[TommasoBendinelli]

Hi @eleanorjboyd,

The bug only occurs when I use listen mode from debugpy:

import debugpy
debugpy.listen(("localhost", 55678))

or with the command line

If I start the debugger from vscode then it works.

[eleanorjboyd]

For the command line, what specifically are you running? Are you attaching to the debugpy instance in the listen case (like how / from where are you starting it)

[rchiodo]

I can reproduce the issue from the VS code terminal with the following command line:

python -m debugpy --listen 0.0.0.0:5678 --wait-for-client .\test_debugattach.py

VS code is just auto attaching and not using my launch.json config or global settings.

[eleanorjboyd]

Thanks everyone for the comments and sorry the new no-config debug is getting in the way of previous workflows. What is happening is we add the environment variable DEBUGPY_ADAPTER_ENDPOINTS to allow us to communicate between the debugger without other setup. So for now you can unset the DEBUGPY_ADAPTER_ENDPOINTS in a terminal (for me with zsh its unset $DEBUGPY_ADAPTER_ENDPOINTS. If you do this (in each new terminal) it is a temp fix.

Long term fix is either I make it so you have to enable no-config debug or I can make it so we only add DEBUGPY_ADAPTER_ENDPOINTS if the user calls no-config debugging. (also long term is we could have it so debugpy allows a folder instead of file for the environment variable but that would require upstream changes).

I am going to go with the second (we only add DEBUGPY_ADAPTER_ENDPOINTS if the user calls no-config debugging) and we can give that a try to see if it makes sense or if we need a new solution. I will put out a fix with that change and let yall know so you can try it. Thanks!