ruby lsp stuck on starting

[milagros-sassenus]

Description

Ruby LSP Information

`

Ruby LSP Information

VS Code Version

1.99.3

Ruby LSP Extension Version

0.8.10

Ruby LSP Server Version

Unknown

Ruby LSP Addons

Ruby Version

2.6.3

Ruby Version Manager

rbenv

Installed Extensions

Click to expand

• project-manager (12.8.0)
• gitlens (17.6.2)
• vscode-pull-request-github (0.108.0)
• go (0.50.0)
• git-graph (1.30.0)
• black-formatter (2025.2.0)
• debugpy (2025.14.1)
• pylint (2025.2.0)
• python (2025.6.1)
• jupyter (2025.3.0)
• jupyter-renderers (1.3.0)
• java (1.46.0)
• ruby-lsp (0.8.10)
• vscode-pets (1.34.0)
• vscode-gradle (3.17.0)
• vscode-java-debug (0.58.2)
• vscode-java-dependency (0.26.2)
• vscode-java-pack (0.30.4)
• vscode-maven (0.44.0)

Ruby LSP Settings

Click to expand

Workspace

{}

User

{
  "enableExperimentalFeatures": false,
  "enabledFeatures": {
    "codeActions": true,
    "diagnostics": true,
    "documentHighlights": true,
    "documentLink": true,
    "documentSymbols": true,
    "foldingRanges": true,
    "formatting": true,
    "hover": true,
    "inlayHint": true,
    "onTypeFormatting": true,
    "selectionRanges": true,
    "semanticHighlighting": true,
    "completion": true,
    "codeLens": true,
    "definition": true,
    "workspaceSymbol": true,
    "signatureHelp": true,
    "typeHierarchy": true
  },
  "featuresConfiguration": {},
  "addonSettings": {},
  "rubyVersionManager": {
    "identifier": "auto"
  },
  "customRubyCommand": "",
  "formatter": "auto",
  "linters": null,
  "bundleGemfile": "",
  "testTimeout": 30,
  "branch": "",
  "pullDiagnosticsOn": "both",
  "useBundlerCompose": false,
  "bypassTypechecker": false,
  "rubyExecutablePath": "",
  "indexing": {},
  "erbSupport": true,
  "useLauncher": false
}

` ### Reproduction steps

Just opening the vs code and then the extension is stuck on starting, I tried downgrading the version but l
uck wasn´t on my side. I have been using ruby lsp since the firsts releases, and then it started failing since a month ago (ish) . I have read another issues where something similar happened, and something that caught my attention was that the project folders where mentioned. The workspace I am trying to run the extension is quite large, so maybe there is a way to optimize it?
Thank you for reading, I hope we find a solution 🙏🏻

[pkondzior]

@milagros-sassenus anything interesting going on in Ruby LSP extension Output ? There might be useful diagnostic information about your environment or project indexing going on in the workspace where you are trying to use RubyLSP. I believe VS Code has panel for this, you can get it VIew -> Output or CMD SHIFT U on MacOS.

[milagros-sassenus]

Sorry I didnt paste the output earlier, here it is:

[pkondzior]

Not sure if Ruby LSP is even starting, maybe turn on tracing:

    "ruby lsp.trace.server": "verbose",

then you should see something like this:

...
2025-10-29 12:41:14.265 [info] () Running command: `/opt/homebrew/bin/rbenv exec ruby -EUTF-8:UTF-8 '/Users/pkondzior/.vscode/extensions/shopify.ruby-lsp-0.9.32/activation.rb'` in /Users/pkondzior/Projects/... using shell: /bin/zsh
2025-10-29 12:42:49.190 [info] () [Trace - 12:42:49] Sending request 'initialize - (0)'.
2025-10-29 12:42:49.190 [info] () Params: {
    "processId": 46881,
...

[schperplata]

I am having the exact same issue on:
OS: Pop_OS! 22.04 LTS
VS Code: Version: 1.105.1
RubyLSP: 0.9.32

Seems like "ruby lsp.trace.server": "verbose", setting (and its variants like "rubyLsp.trace.server": "verbose",) are not recognized by this setup. The output therefore is only:

2025-10-30 15:18:08.075 [info] (predict_leads) Running command: `rbenv exec ruby -EUTF-8:UTF-8 
'/home/domen/.vscode/extensions/shopify.ruby-lsp-0.9.32/activation.rb'` in /home/domen/pl_code/predict_leads using shell: /usr/bin/bash

[vinistock]

I suspect @schperplata problem is different from @milagros-sassenus.

@schperplata: the VS Code extension needs to be able to invoke your shell with access to your version manager to correctly reproduce the same environment inside the NodeJS process.

1. The shell being reported to the extension by VS Code is /usr/bin/bash. Is that the one you use? Maybe the default shell is not configured in VS Code the same way as it is for the terminal?
2. Is rbenv always sourced in your preferred shell configurations?

@milagros-sassenus for your issue, it's a bit hard to diagnose because we don't have much information other than the fact it's stuck.

1. Does this happen on every project you have?
2. I noticed you're using Cursor. Does it also happen in VS Code?
3. If you run the activation script manually, does it also hang or does it print a bunch of environment variables?

/opt/homebrew/bin/rbenv exec ruby ...

[schperplata]

Hey @vinistock , sorry for the late reply and thanks for help. In past week I've been reinstalling OS, and all VS code related issues are now gone.
Before that, I've checked all those things you suggested, and configuration seemed OK - however, something caused terminal in VS Code (the one for RubyLSP related tasks) to have different environment than the terminals I spawn (also in VS Code, integrated). I couldn't figure out what was the cause, but since it didn't work in any combination of disabled extensions and settings, I gave up. I even reinstalled VS Code and all the extensions.
I know it is hard to debug these things with so little info, so for now, my issue is resolved. Thank you.

[egiurleo]

Hi @milagros-sassenus! I noticed you're using a really old version of Ruby. Stable releases are 3.4.7, 3.3.10, and 3.2.9. We don't test the LSP against unsupported Ruby versions and can't guarantee it'll work. I'm going to close this issue -- if you encounter the same problem on a recent Ruby version, feel free to open it up again and let us know!