Debug: couldn't start dlv-dap

[hyangah]

https://stackoverflow.com/questions/68753251/couldnt-start-dlv-dap

launch.json:

{
"version": "0.2.0",
"configurations": [
    {
        "name": "Launch file",
        "type": "go",
        "request": "launch",
        "mode": "debug",
        "program": "${workspaceFolder}",
        "showLog": true,
        "env": {
            "GO111MODULE": "on"
        }
    }
]
}

I suspect the default timeout (5sec) is too short, or some other bug prevented the dlv dap server from starting:

If any of you encountered an issue, can you please try the following command and time how long it takes?

$ dlv-dap dap --listen=:12345 --log --log-output=dap

[miao233]

i have this issue as well

[miao233]

i have this issue as well

i have fixxed it but dlv-dap doesn't work

add this config into "setting.json"

"go.alternateTools": {
    "dlv": "dlv"
    },
    "go.delveConfig": {

        "dlvLoadConfig": {
            "followPointers": true,
            "maxVariableRecurse": 1,
            "maxStringLen": 64,
            "maxArrayValues": 64,
            "maxStructFields": -1
        },
        "apiVersion": 2,
        "showGlobalVariables": false,
        "debugAdapter": "legacy",
        "substitutePath": []
    }

but,command "dlv-dap dap --listen=:12345 --log --log-output=dap" doesn't work

[hyangah]

@miao233 Please share what you see when you run "dlv-dap dap --listen=:12345 --log --log-output=dap". If you are using windows, find where your dlv-dap.exe is installed and run `dlv-dap.exe dap --listen=:12345 --log --log-output=dap"

[malaclypse]

I'm not the original poster, but since I also ran into this issue, I thought I'd comment here to follow.
I'm on Windows with the latest VSCode and Go, and since I also see this issue (but not all the time), I assume that the 5 second timeout is definitely too short, is there a good reason why it was set to 5 seconds specifically? Is there an easy way to increase it?

The output of the above command is fine, the DAP server starts successfully.

DAP server listening at: [::]:12345
2021-08-16T19:40:49+03:00 debug layer=dap DAP server pid = 24672

[hyangah]

@malaclypse 5sec is arbitrarily chosen - the command (dlv dap) does not do anything significant other than starting a tcp server on the given port. Not sure what makes it to take such a long time in reasonably performant development environment. When you ran the command, did it take long time to see the output?

[momkeller]

@hyangah, i also run into this - vs code v1.59, go v1.16.7 - when i run the dlv dap command listed above manually, it takes about 14 seconds.

[gopherbot]

Change https://golang.org/cl/342632 mentions this issue: src/goDebugFactory: increase timeout for dlv dap server start

[miao233]

@hyangah i found the problem,cause firewall & safety-critical software had stopped dlv-dap on Windows with the latest VSCode and Go.i think maybe dlv-dap is new for windows? anyway,it work, it takes about 2 seconds.

[malaclypse]

@hyangah I see now that if I run start the server in a terminal outside of VSCode it's instantaneous, but it takes between 7 and 9 seconds inside the VSCode terminal, I'm honestly not sure what could be causing the discrepancy. I'm using the Windows Terminal app when outside of VSCode as my terminal, and it doesn't matter if I'm running it in CMD or a Powershell Core session (same for VSCode, in any shell it's much slower).

[gopherbot]

Change https://golang.org/cl/345550 mentions this issue: [release] src/goDebugFactory: increase timeout for dlv dap server start