!MESSAGE Cannot run program "kill": error=316, posix_spawn failed I tracked it in a new issue !ENTRY .core 4 0 21:04:11.286 In another VS Code window, when I click x to close VS Code, the ParentProcessWatcher mechanism actually didn’t work either. Stack trace: Error: Cannot call write after a stream was destroyedĪt new NodeError (node:internal())Īt _write (node:internal())Īt Socket.write (node:internal())Īt ()Īt c.write (())Īt _.doWrite (()) Rejected promise not handled within 1 second: Error : Cannot call write after a stream was destroyed Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:104Īt WriteWrap.onWriteComplete (node:internal())Īt WriteWrap.callbackTrampoline (node:internal())
Rejected promise not handled within 1 second: Error: write EPIPE Java spinning wheel spinning in the bottom right corner.The spinning wheel just keeps going in the bottom-right corner.
Exceptions activating vscode-java extension.
0 kommentar(er)
