Use a workspace to port map instead of single value file

[vinistock]

Motivation

There's currently a bug that if you open a second VS Code window, it will override our port file with a new value, disconnecting the first window from being able to report test statuses.

We can solve this problem by using a JSON file instead of a single value file and then writing to it a map of workspaceFilePath => port.

That way, the only time there's a disconnect is if you open the same exact workspace in two different editor windows, which I believe is fine. Trying to use vscode.env.sessionId would be difficult because the LSP reporter instance doesn't have a way to know what session owns the execution - especially when running manually through the terminal.

Implementation

Started writing a map of workspaceFilePath => port and, in the reporter side, started reading it. We kept the reading of the old file just to avoid breaking changes while this rolls out.

[vinistock]

• Use a workspace to port map instead of single value file #3502 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label graphite-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[st0012]

Instead of writing to tmp folders, does it make sense to write it to each workspace's .ruby-lsp folder instead?

[vinistock]

Instead of writing to tmp folders, does it make sense to write it to each workspace's .ruby-lsp folder instead?

All workspaces under the current VS Code instance report to the same port, so it made more sense to me to not tie it to any specific workspace. Otherwise, we'd need to write the port file to all workspaces even if you're not using the test explorer there.