VSCode extension seems to hang

[robjackstewart]

Describe the bug
Upon opening any given repository in VSCode, I can see from the logs that the language server has started from the DevSkim VS Code Client output logs, however, nothing else happens.

To Reproduce
Steps to reproduce the behavior:

1. Run devskim analyze -I . in a repository that has devskim items to address
2. Confirm that there is some output from the previous command
3. Open the repository in VSCode
4. Install the DevSkim extensions if it is not already installed
5. Click on Output tab (Ctrl+Shift+U)
6. Select DevSkim VS Code Client form the sources dropdown on the right hand side
7. Observe logs stating that language server has started
8. Navigate to a file that contains problems identified in step 1
9. Observe that nothing identifies the problem

Expected behavior
VSCode should visually identify the problems that were found by running devskim analyze -I . in the same repository.

Screenshots

Versions(please complete the following information):

• OS:
  • Windows 10.0.22621 Build 22621
  • WSL - Ubuntu 20.04.6 LTS
• Devskim CLI: 1.0.8
• Devskim VSCode Extension: 1.0.8

Additional context
Example:

The following image shows a TODO comment that is not identified as a problem in VSCode with the DevSkim extension running:

But running the CLI identifies the problem correctly:

[gfs]

@robjackstewart The issue you're seeing may be related to the issue that will be fixed by #559, but I don't see this specific behavior specifically at this time with either the published or fixed versions when scanning files on the windows file system from a windows VS Code window on a fresh install of Windows 10.

I notice that you list a WSL version, and the interface here shows "WSL" as part of the project name. Can you clarify how WSL is being used here so I can attempt to more accurately reproduce this?

[gfs]

Closed due to no repro on latest version. Feel free to reopen this or open a new issue with the additional details requested about how WSL factors in here if you're still experiencing this problem.