Would it be OK to create a task to start a debugpy session and then use that task as a `preLaunchTask` in launch config

[balaji]

What I really want to do:

• Use remote attach to debug a python debugpy session
• I want this to be a single click, i.e. I don't want to run the debugpy session first and then click on the "Run and Debug" button. The idea is inspired from this blog post

What I did

• In tasks.json file

  {
    "label": "python debug",
    "type": "shell",
    "isBackground": true,
    "command": "${workspaceFolder}/py-start-debug",
    "presentation": {
      "reveal": "silent",
      "showReuseMessage": false,
      "clear": true,
      "close": true
    },
    "problemMatcher": [
      {
        "pattern": [
          {
            "regexp": ".",
            "file": 1,
            "line": 1,
            "column": 1,
            "message": 1
          }
        ],
        "background": {
          "activeOnStart": true,
          "beginsPattern": { "regexp": "." },
          "endsPattern": { "regexp": ".*Note: Debugging will proceed.*" }
        }
      }
    ]
  }

• The shell file (py-start-debug) - simplified:

#!/usr/bin/env bash
python -m debugpy --listen localhost:5678 --wait-for-client --log-to /tmp/debugpylogs example.py

• The launch.json:

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

What happens:

The debug session works. Sometimes in the first attempt. Sometimes in the second attempt.

Debugging working in First attempt:

Debugging working in Second Attempt:

Logs:

First Attempt Success.zip Second Attempt Success.zip

Test Code:

source.zip

Question:

Why would it work sometimes in the first attempt itself and why would it work only in the second attempt?

[paulacamargo25]

Thanks for your issue report, that depends on how vscode handles the attach, if the problem persists could you create an issue in the vscode repository? thank you