You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if that is a bug with extension but I seen random but often enough failures to start the testing with a recursive set of popup errors like:
Popup dialog
Title: A JavaScript error occurred in the main process
Uncaught Exception:
Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:164:15)
at writeGeneric (node:internal/stream_base_commons:155:3)
at Socket._writeGeneric (node:net:795:11)
at Socket._write (node:net:807:8)
at writeOrBuffer (node:internal/streams/writable:389:12)
at _write (node:internal/streams/writable:330:10)
at Socket.Writable.write (node:internal/streams/writable:334:10)
at console.value (node:internal/console/constructor:285:16)
at console.warn (node:internal/console/constructor:364:26)
at process.<anonymous> (/Users/ssbarnea/c/a/vscode-ansible/.vscode-test/vscode-darwin-1.68.1/Visual Studio Code.app/Contents/Resources/app/out/bootstrap.js:1:401)
at process.emit (node:events:390:28)
Console:
Found /Users/ssbarnea/c/a/vscode-ansible/.vscode-test/vscode-darwin-1.68.1. Skipping download.
(node:93197) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Electron --trace-deprecation ...` to show where the warning was created)
Installing extensions...
Extension 'ansible-0.10.0-next-1.vsix' was successfully installed.
Installing extensions...
Extension 'ms-python.python' is already installed.
Installing extensions...
Extension 'redhat.vscode-yaml' is already installed.
"/Users/ssbarnea/c/a/vscode-ansible/.vscode-test/vscode-darwin-1.68.1/Visual Studio Code.app/Contents/Resources/app/bin/code" --user-data-dir=/Users/ssbarnea/c/a/vscode-ansible/out/userdata --extensions-dir=/Users/ssbarnea/c/a/vscode-ansible/out/ext --list-extensions --show-versions
[email protected][email protected][email protected][email protected][email protected][email protected][email protected]
node:events:505
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on ClientRequest instance at:
at TLSSocket.socketErrorListener (node:_http_client:454:9)
at TLSSocket.emit (node:events:527:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -54,
code: 'ECONNRESET',
syscall: 'read'
}
task: Failed to run task "test-e2e": exit status 1
Other
While the console app finished, the broken code app is in an apparent recursive popup mode and the only way to close it is using "Force Quit" (normal no enough) from Dock or Activity Monitor.
The text was updated successfully, but these errors were encountered:
ssbarnea
changed the title
Random error starting tests on mac
macos: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
Jun 26, 2022
That is very weird, apparently there are no changes is just that runnings tests works only when the folder does not exists, so the app is freshly unarchived there. Second time you run, it will fail.
Still starting code app manually from this temp folder seems to be working. Running out of ideas...
I am not sure if that is a bug with extension but I seen random but often enough failures to start the testing with a recursive set of popup errors like:
Popup dialog
Title: A JavaScript error occurred in the main process
Console:
Other
While the console app finished, the broken code app is in an apparent recursive popup mode and the only way to close it is using "Force Quit" (normal no enough) from Dock or Activity Monitor.
The text was updated successfully, but these errors were encountered: