Strange output at the end of the js file debug

未關閉
#1,370 4 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
javascript, node.js
領域
devtools

研究方向

首先重複重現 Node 程式的偵錯步驟,並檢查 dapDebugServer.js,尤其是 stack trace 中第 91 行和第 148 行附近顯示的位置。比較顯示 JSON、主控台輸出或 EPIPE 錯誤的執行結果;當重複偵錯不再產生所回報的 socket 錯誤或非預期的偵錯回應時,即視為完成。

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
Java
星號
203
分支
76
平均合併
1 天 5 小時
30 天內合併 PR
30

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

eclipse-wildwebdeveloper/wildwebdeveloper 的其他 Issue

查看 eclipse-wildwebdeveloper/wildwebdeveloper 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。