When Ruby LSP: Restart failed due to ruby-lsp crashing, the failure will be propagated all the way to VSCode. Then VSCode will prevent the user from rerunning Ruby LSP: Restart again, even though it may not crash this time. Below is an example error message:
This creates development hassle because the user (usually developer) needs to reload the entire VSCode window instead (Developer: Reload Window).
@vinistock suggested that we can catch the execution failure from the extension (may be this line?) to avoid this issue.
When
Ruby LSP: Restartfailed due toruby-lspcrashing, the failure will be propagated all the way to VSCode. Then VSCode will prevent the user from rerunningRuby LSP: Restartagain, even though it may not crash this time. Below is an example error message:This creates development hassle because the user (usually developer) needs to reload the entire VSCode window instead (
Developer: Reload Window).@vinistock suggested that we can catch the execution failure from the extension (may be this line?) to avoid this issue.