debug.javascript.autoAttachFilter setting is not respected

[cruzj6]

Describe the bug
The debug.javascript.autoAttachFilter setting is not respected. autoAttachMode is always set to always in VSCODE_INSPECTOR_OPTIONS.

Here's the command it's using when I run the launch config:

/usr/bin/env 'NODE_OPTIONS=--require /home/node/.vscode-server/bin/5d424b828ada08e1eb9f95d6cb41120234ef57c7/extensions/ms-vscode.js-debug/src/bootloader.bundle.js --inspect-publish-uid=http' 'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"/tmp/node-cdp.182-2.sock","deferredMode":false,"waitForDebugger":"","execPath":"/usr/local/bin/node","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"/tmp/node-debug-callback-559cc875db498717"}' /usr/local/bin/node ./runServices.js 

To Reproduce
Steps to reproduce the behavior:

1. Set debug.javascript.autoAttachFilter either via the UI or settings.json to anything except always (disabled probably simplest)
2. Create a launch.json config with type node and request launch that spawns a node process that shouldn't be attached to due to the auto attach filter.
3. Run the config
4. Notice the debugger attaches to every node process and sub-process that runs

Log File

(emailed)

VS Code Version: 1.53.1

Additional context
Here's my settings - as you can see it is disabled:

Also it shows the mode correctly in the editor's footer when I change it to smart or onlyWithFlag, but that's not reflected when it actually runs the command:

Here's my launch config in launch.json:

    {
      "type": "node",
      "request": "launch",
      "name": "Run All Services",
      "program": "${workspaceFolder}/runServices.js",
      "sourceMaps": true,
      "outFiles": ["${workspaceFolder}/services/*/.webpack/**/*.js"],
      "skipFiles": [
        "${workspaceFolder}/**/node_modules/**/*.js",
        "<node_internals>/**/*.js"
      ],
      "resolveSourceMapLocations": [
        "${workspaceFolder}/**",
        "!**/node_modules/**"
      ],
      "trace": true,
    },

[connor4312]

1. Create a launch.json config with type node and request launch that spawns a node process that shouldn't be attached to due to the auto attach filter.
2. Run the config
3. Notice the debugger attaches to every node process and sub-process that runs

This is intended -- auto attach does not affect defined configurations in launch.json's at all.

If you don't want to attach to children of the configuration, you can set this by setting "autoAttachChildProcesses": false. (Will show as invalid unless the launch type is updated to pwa-node, but will still work)

[cruzj6]

@connor4312 Thanks for the clarification! I will give this a go.