pants test --debug-adapter src/python/pants/backend/cc/lint/clangformat/rules_integration_test.py

{
  "configurations": [
    {
      "name": "Python Debugger: Remote Attach",
      "type": "debugpy",
      "request": "attach",
      "connect": {
        "host": "localhost",
        "port": 5678
      },
      "pathMappings": [
        {
          "localRoot": "${workspaceFolder}",
          "remoteRoot": "."
        }
      ]
    }
  ]
}

Similar in the

example-python

hello-world

cc @thousands-plumber-33255 ^^ Did you get your issue solved?

thanks for looking into this 🙂

ok I did have a test for this in the test repo, and it worked, however in my main project (closed source) it did not. comparing pants and pytest configs now

update: I added a simple test

def test_math():
    qweert = 123
    print(qweert)
    assert 1 + 1 == 2

with a breakpoint on the print line, this still did not catch - it must be something about the repo setup. The pants version is 2.29.0 in both repos, looking for differences between the setups

Also, what OS/environment are you on?

I'm wondering if one of the recent changes might be relevant: https://github.com/microsoft/debugpy/releases

both constraint lines are: • interpreter_constraints = ["==3.12.*"] the os is wsl2 with Ubuntu 24.0.4.3 LTS, so pretty standard debugpy is at 1.8.16 in bth - checking the microsoft link now

that reported attach bug is for 3.11 checking more in depth now

hmm that doesn't seem to be similar enough

But you said your test repo works in wsl?

vscode logs do not say much, just the followign in both cases: 2025-10-27 112327.895 [info] Connecting to DAP Server at: 127.0.0.1:5678 2025-10-27 112335.711 [info] Resolving attach configuration with substituted variables 2025-10-27 112335.719 [info] Connecting to DAP Server at: 127.0.0.1:5678 2025-10-27 115825.336 [info] Resolving attach configuration with substituted variables 2025-10-27 115825.344 [info] Connecting to DAP Server at: 127.0.0.1:5678

looking through the archives https://pantsbuild.slack.com/archives/C046T6T9U/p1668399648191449

hmm, that was theoretically fixed, here - https://github.com/pantsbuild/pants/pull/17566/files - but maybe a regression, I'm trying to turn off the sandbox - but why did it work in one repo and not in another one?

how do I run debugpy in verbose mode?

some argument inside launch.json?

ah wait so it goes to the server, not the cvscode client

now looking to parse it to find the information how to fix it

okay it's just directly not dectecting the breakpoints on the server side (the pants process), bbreakpoint in file that does ont exist

• https://github.com/microsoft/PTVS/issues/7236 • https://github.com/microsoft/PTVS/issues/6610#issuecomment-1692724477 - here it's recommended to setup localRoot as devcontainer path and remotePath the debugging container - however I am not using a devcontainer, trying options how to set it up right

https://github.com/microsoft/debugpy/issues/1858#issuecomment-2706772617 tried this fix, didn't work as expected

well, will try tomorrow

good morning, returning to testing this

one new idea - to start from a known working state and just add things to get the final functionality - maybe all will align well, some odd path-dependance specific to that other repo?

okay, fixed on my end by moving into a new repo. how to set the debugpy server from the IDE, not through the CLI? or how to specify a specific test within a file rather than all tests in a file?