[VSCode] Stuck Activating Until Switched to New File

[calmacleod]

Description

The Ruby environment fails to activate until a different file than is already open is selected in vscode

Reproduction steps

1. Using the latest version of vscode and Ruby-LSP with rbenv (The connection is over SSH but I haven't tried this locally)
2. Start up vsocde and message stating environment is being activated is present in the lower corner
   
3. Environment remains in activating state until another different file is selected.
4. There is no output from the extension until a new file is selected
   
5. I've been seeing this the past few versions with no change in behavior

[vinistock]

Thank you for the bug report! After you open the file, does the Ruby LSP work properly? And are you using multiple workspaces?

We did switch to a lazy approach to activating the Ruby LSP because users with too many workspaces had performance issues if we tried to eagerly boot too many language servers.

If the scenario described matches what you're doing, then this is just a messaging issue. We always start by showing "Activating Ruby environment", but it's actually not doing anything until the lazy activation is triggered.