Stopping a session from call stack actions view always goes to the active session

[connor4312]

Version: 1.45.0-insider (user setup)
Commit: a0fe37870c42e0704a492cdc6b8550b4cf23f63c
Date: 2020-04-30T05:39:08.281Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

1. Have two launch configs running, A and B
2. Select launch config A from the call stack view
3. Click stop/disconnect on config B
4. Config A exits

Recording: https://memes.peet.io/img/20-04-08083092-2b69-4405-9d53-93cf511622ec.webm

[isidorn]

I can not reproduce this with just a simple example. Here are my steps.
Have the following program and have two launch configs which break on it

debugger;
console.log('hello connor')

Click stop on an unfocused one -> the correct one gets stopped.
In case you want to investiate more. Put a breakpoint here and checkout what is the context and on which Session the disconnect gets sent.

[connor4312]

Looking into it some more, this seems to happen only with attach. I can easily reproduce it with two launch configs like:

    {
      "type": "pwa-node",
      "request": "attach",
      "trace": true,
      "name": "[Node] Attach to program",
      "port": 9229
    },
    {
      "type": "pwa-node",
      "request": "attach",
      "trace": true,
      "name": "[Node] Attach to program2",
      "port": 9229
    },

[isidorn]

@connor4312 thanks for providing more details. Yes the disconnect command was not respecting the context passed properly. I have pushed a fix.