Language server auto kill process when using ssh #833
+394
−19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #726
fixes #817
Summary
Added two new settings: teroshdl.cleanup.killServerProcesses.enabled (default false) and teroshdl.cleanup.killServerProcesses.gracePeriodMs (ms).
Implemented safe cleanup in rust_hdl.ts and verible.ts: pgrep -f via execFile, PID validation, send SIGTERM then SIGKILL after the grace period.
Cleanup runs only when enabled and the session is Remote‑SSH (vscode.env.remoteName check).
Added a Web UI indicator + commands (teroshdl.cleanup.openSettings)
Why I implemented the config option in VS Code settings:
VS Code settings give per-scope granularity: User (global), Workspace (project), and Remote (per-SSH-host).
Tests
I could not debug Teros extension when using it over SSH. So I had to build a release and test it.
Disabled
Enabled