Strange output at the end of the js file debug

首先重复复现 Node 程序的调试步骤，并检查 dapDebugServer.js，尤其是 stack trace 中第 91 行和第 148 行附近显示的位置。比较显示 JSON、控制台输出或 EPIPE 错误的运行结果；当重复调试不再产生报告中的 socket 错误或意外的调试响应时，即视为完成。

Sometimes, I get a strange output in the console at the end of debugging. The output is:

Debug server listening at 127.0.0.1:44301
{
  seq: 286,
  type: 'response',
  request_seq: 13,
  command: 'disconnect',
  success: true,
  body: {}
}
{
  seq: 287,
  type: 'response',
  request_seq: 14,
  command: 'disconnect',
  success: true,
  body: {}
}
{
  seq: 11,
  type: 'response',
  request_seq: 8,
  command: 'disconnect',
  success: true,
  body: {}
}
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (node:net:569:14)
    at iv.send (/home/user/Programas/eclipse/plugins/org.eclipse.wildwebdeveloper_1.1.2.202310160731/js-debug/src/dapDebugServer.js:148:162)
    at df._send (/home/user/Programas/eclipse/plugins/org.eclipse.wildwebdeveloper_1.1.2.202310160731/js-debug/src/dapDebugServer.js:91:4596)
    at df._onMessage (/home/user/Programas/eclipse/plugins/org.eclipse.wildwebdeveloper_1.1.2.202310160731/js-debug/src/dapDebugServer.js:91:5086)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EPIPE'
}

Node.js v18.18.0

It is important to note that this error is not shown every time. Sometimes it happens, sometimes it doesn't.

Steps to reproduce:

• Create a js file with the following code:

console.log("test")

• Put a breakpoint in the console.log line
• Right click on the file body.
• Select "Debug As -> Node program"
• Press f8 to continue the debug
• Repeat the debug several times

Sometimes the error is not shown. Sometimes only the json is shown. Sometimes only console.log output is shown.

I hope that every time the debug occurs, only the console.log output is shown.

It appears that some process is trying to write in a socket but it has already been terminated.