Post

Who's actually using #Ruby LSP in #VSCode to run tests? I am trying it out today and its command to run all tests from current file seems to be running *each test scenario* in a separate process. This means that running all tests is dead slow. Am I doing something wrong?

Vinicius Stock

@vinistock.bsky.social

6 May 2025

We’re literally about to release our reimplementation of the explorer, which fixes this and many other shortcomings

Peter Solnica 🇺🇦 🇵🇱 🇪🇺

@solnic.dev

7 May 2025

Unfortunately it stopped working completely for me in getsentry/sentry-ruby 🥺

Vinicius Stock

@vinistock.bsky.social

7 May 2025

We didn’t roll anything out yet. Did you enable it yourself?

Peter Solnica 🇺🇦 🇵🇱 🇪🇺

@solnic.dev

7 May 2025

Oh, I just updated to latest version today. Something is very broken though as previous version gives me the same result. It only happens inside a devcontainer.

Ufuk Kayserilioglu

@ufuk.dev

Latest version of the gem or the VSCode extension? Not sure, but the gem update might not work correctly without the newer extension.

7/5/25, 8:53 pm0 reposts0 likes

Peter Solnica 🇺🇦 🇵🇱 🇪🇺

@solnic.dev

8 May 2025

I just fixed it - Ruby LSP couldn't figure out where the ruby exec is and I had to provide its path explicitly. The error was confusing though and in general handling of ruby exec is problematic so I'm gonna report an issue /cc @vinistock.bsky.social

Peter Solnica 🇺🇦 🇵🇱 🇪🇺

@solnic.dev

8 May 2025

I use the latest version of the extension and I just updated server gem and it gives me the same result - trying to run a test shows "No workspace found".