When terminating vscode or an rsp-server directly, it's possible that the workspace lock file is never removed. On the next startup attempt, the rsp may refuse to start because the workspace is locked. vscode-server-connector should try to work around this by checking if the port named in teh lock file is still in use and possibly delete the lock file before starting the rsp.
When terminating vscode or an rsp-server directly, it's possible that the workspace lock file is never removed. On the next startup attempt, the rsp may refuse to start because the workspace is locked. vscode-server-connector should try to work around this by checking if the port named in teh lock file is still in use and possibly delete the lock file before starting the rsp.