vscode: EPIPE write failure while debugging after upgrading to 1.49

VSCode Version: 1.49
OS Version: Pop OS 20.04 (Ubuntu)

Steps to Reproduce:

Upgrade to 1.49
Trying to debug

Does this issue occur when all extensions are disabled?: Yes

After upgrading to 1.49, both a Linux Pop OS machine and a Mac OSX machine on my team started having the following error: When attempting to launch the debugger, we would receive a failure to write EPIPE error. The error triggers in the tslib package. In our particular situation, it starts with an attempt to createConnection() with the TypeORM package (which uses node-mssql and tedious). Stepping into that breakpoint trigger the tslib failure and the EPIPE message.

Rolling back to VSCode 1.48 eliminated the problem.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 4
Comments: 18 (9 by maintainers)

Links to this issue

javascript - VSCODE: No debug adapter, can not send 'variables'" - Stack Overflow

Commits related to this issue

fix: process.stderr being incorrectly destroyed This was intended to destroy a pipe reader, but that reader was removed at some point and this code was left in there. Interestingly it does not seem t... — committed to microsoft/vscode-js-debug by connor4312 4 years ago
debug: update js-debug For https://github.com/microsoft/vscode/issues/106484 — committed to microsoft/vscode by connor4312 4 years ago
Improve debugging experience * Make debugger work in VS Code 1.49 by adding outputCapture workaround [https://github.com/microsoft/vscode/issues/106484#issuecomment-691202789] * Elide node_modules fr... — committed to apparebit/siteforge by apparebit 4 years ago

Most upvoted comments

I think I found the issue! Please try adding “outputCapture”: “std”, in your launch.json as a workaround (may need to change type to pwa-node for it to be seen as valid).

This fixes the issue for me; let me know if it does the same for you.

+10

connor4312 on Sep 11, 2020

Awesome, thank you for confirming. I will put in a fix for the recovery release.

connor4312 on Sep 11, 2020

Actually "debug.javascript.usePreview": false does resolve the problem on my side.

maximedupre on Sep 11, 2020

Oh btw, it didn’t work 😛

nico93f on Sep 11, 2020

Does it make a difference if you:

comment out the “preLaunchTask”?

add "debug.javascript.usePreview": false as a user setting?

(only one at a time, not both)

Same problem,

I dont have preLaunchTask and the usePreview: false didn’t work

nico93f on Sep 11, 2020

See the solution here https://github.com/microsoft/vscode/issues/106484#issuecomment-691202789