Unable to debug with SAM local invoke in Node.js example

[cbertozzi]

Hi all,
in nodejs-example-extension example for Node.js platform something during registration phase brakes the debugger when runs locally on VS Code using sam local invoke --port 6767 ... on a Lambda that includes this layer.
The following is a snap of the debug logs when launched from VS Code:

START RequestId: 05da599b-f76d-494e-905b-bead9860f186 Version: $LATEST
nodejs-example-extension  launching extension
Debugger listening on ws://0.0.0.0:6767/95282789-af6d-4c40-b544-b1d70e0650c2
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
hello from extension
register
extensionId 0e16eae5-5e84-4b22-a204-c54424793f69
next
Starting inspector on 0.0.0.0:6767 failed: address already in use
invoke
next
...

notice the Starting inspector on 0.0.0.0:6767 failed: address already in use error line in logs, after that all set breakpoints are ignored and it's impossible to debug every Lambdas.

this is the VS Code debug task setup:

{
        "name": "lambda_with_example_layer",
        "type": "pwa-node",
        "request": "attach",
        "address": "localhost",
        "port": 6767,
        "localRoot": "${workspaceFolder}/lambda_with_example_layer",
        "sourceMaps": true,
        "remoteRoot": "/var/task",
        "protocol": "inspector",
        "stopOnEntry": false,
        "skipFiles": [
          "<node_internals>/**"
        ]
}

Is there any debugger/SAM/Docker configuration that i missed? Or is something else deeper in the layer execution flows that broke debugging in a container with SAM local?

[BrunoDonini]

+1

[andreadallura]

+1

[mcozzoli87]

+1

[danielivanovz]

+1

[massimoneri]

+1

[VonSerpe]

+1

[aberni-bepower]

+1