ungraceful client disconnect. nothing to worry about?

[dkebler]

I get this same set of logs every time I reload the browser. When client reconnects all is fine. I assume this is a nothing concerning just the last dying gasps of a broken connection and can be ignored>

As so why I reloaded the page it seems that adding items to .gitignore, vscode won't update the new status of those files and directories until a reload.

mydoc  | [14:43:44] [172.0.8.1][a1e6e6ab][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
mydoc  | [14:43:44] [172.0.8.1][6e7a67cf][ExtensionHostConnection] <125541> Extension Host Process exited with code: 0, signal: null.
mydoc  | File not found: /usr/local/lib/code-server/lib/vscode/out/vsda_bg.wasm
mydoc  | File not found: /usr/local/lib/code-server/lib/vscode/out/vsda.js
mydoc  | [14:43:44] [172.0.8.1][a237e6cb][ManagementConnection] New connection established.
mydoc  | [14:43:44] [172.0.8.1][0ebd362d][ExtensionHostConnection] New connection established.
mydoc  | [14:43:44] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment: Unexpected exit code from spawned shell (code 1, signal null)
mydoc  |     at /usr/local/lib/code-server/lib/vscode/out/vs/server/node/server.main.js:96:2471
mydoc  |     at runMicrotasks (<anonymous>)
mydoc  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
mydoc  |     at async /usr/local/lib/code-server/lib/vscode/out/vs/server/node/server.main.js:67:19784
mydoc  | [14:43:44] [172.0.8.1][0ebd362d][ExtensionHostConnection] <250265> Launched Extension Host Process.
mydoc  | [14:43:44] ptyHost was unable to resolve shell environment Error: Unable to resolve your shell environment: Unexpected exit code from spawned shell (code 1, signal null)
mydoc  |     at /usr/local/lib/code-server/lib/vscode/out/vs/server/node/server.main.js:96:2471
mydoc  |     at runMicrotasks (<anonymous>)
mydoc  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
mydoc  |     at async /usr/local/lib/code-server/lib/vscode/out/vs/server/node/server.main.js:67:19784
mydoc  | IPC "File Watcher" crashed with exit code null and signal SIGSEGV
mydoc  | [14:43:45] [File Watcher (universal)] restarting watcher after error: terminated by itself with code null, signal: SIGSEGV
mydoc  | IPC "File Watcher" crashed with exit code null and signal SIGSEGV
mydoc  | [14:43:45] [File Watcher (universal)] restarting watcher after error: terminated by itself with code null, signal: SIGSEGV
mydoc  | IPC "File Watcher" crashed with exit code null and signal SIGSEGV
mydoc  | [14:43:45] [File Watcher (universal)] restarting watcher after error: terminated by itself with code null, signal: SIGSEGV
mydoc  | IPC "File Watcher" crashed with exit code null and signal SIGSEGV
mydoc  | [14:43:45] [File Watcher (universal)] restarting watcher after error: terminated by itself with code null, signal: SIGSEGV
mydoc  | IPC "File Watcher" crashed with exit code null and signal SIGSEGV
mydoc  | [14:43:45] [File Watcher (universal)] restarting watcher after error: terminated by itself with code null, signal: SIGSEGV
mydoc  | IPC "File Watcher" crashed with exit code null and signal SIGSEGV
mydoc  | [14:43:45] [File Watcher (universal)] gave up attempting to restart watcher after error: terminated by itself with code null, signal: SIGSEGV

[code-asher]

Some of these look worrying to me, but maybe not critical.

resolving shell environment failed

VS Code tries to spawn a shell to get your latest environment, but this is only really important if you add new environment variables after spawning code-server. You would need to look into things like your bashrc and see if there is something causing an issue. I think if you run with `--log trace` VS Code will tell you the command they are trying to spawn, so you could run that command yourself to debug it.

restarting watcher after error: terminated by itself with code null, signal: SIGSEGV

Really not too sure about this one. You mentioned that the .gitignore is not picked up until you reload, and this could be why. I am not familiar enough to say why it might be crashing though so you might have better luck asking the VS Code folks.