rbenv not working properly

[baelter]

Description

rbenv version is not respected/loaded properly. Details below.

Ruby LSP Information

VS Code Version

1.97.2

Ruby LSP Extension Version

0.9.7

Ruby LSP Server Version

Unknown

Ruby LSP Add-ons

Ruby Version

3.3.5

Ruby Version Manager

rbenv

Installed Extensions

Click to expand

• EditorConfig (0.17.1)
• RunOnSave (0.2.7)
• ansible (25.2.0)
• auto-add-brackets (0.12.2)
• code-spell-checker (4.0.40)
• copilot (1.275.0)
• copilot-chat (0.24.1)
• crystal-ameba (0.2.1)
• crystal-lang (0.9.7)
• custom-local-formatters (0.1.1)
• debug (0.27.0)
• debugpy (2025.0.1)
• dotenv (1.0.1)
• doxdocgen (1.4.0)
• errorlens (3.23.0)
• gitlens (16.3.2)
• haml (1.4.1)
• haml-lint (0.2.1)
• isort (2023.10.1)
• jinjahtml (0.20.0)
• makefile-tools (0.12.17)
• markdown-mermaid (1.27.0)
• mermaid-markdown-syntax-highlighting (1.7.0)
• output-colorizer (0.1.2)
• project-manager (12.8.0)
• python (2025.0.0)
• rainbow-csv (3.17.0)
• remote-containers (0.397.0)
• remote-explorer (0.4.3)
• remote-ssh (0.117.1)
• remote-wsl (0.88.5)
• ruby-extensions-pack (0.1.13)
• ruby-lsp (0.9.7)
• shellcheck (0.37.7)
• sorbet-vscode-extension (0.3.39)
• systemd-unit-file (1.0.6)
• terraform (2.34.3)
• todo-tree (0.0.226)
• vscode-eslint (3.0.10)
• vscode-github-actions (0.27.1)
• vscode-gradle (3.16.4)
• vscode-html-css (2.0.13)
• vscode-kubernetes-tools (1.3.20)
• vscode-lldb (1.11.4)
• vscode-markdownlint (0.59.0)
• vscode-pull-request-github (0.104.1)
• vscode-pylance (2025.2.1)
• vscode-rdbg (0.2.2)
• vscode-sort-json (1.20.0)
• vscode-speech (0.12.1)
• vscode-template-literal-editor (0.10.0)
• vscode-yaml (1.16.0)
• vsliveshare (1.0.5948)
• workspacesort (1.6.2)

Ruby LSP Settings

Click to expand

Workspace

{}

User

{
  "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": "rbenv"
  },
  "customRubyCommand": "",
  "formatter": "auto",
  "linters": null,
  "bundleGemfile": "",
  "testTimeout": 30,
  "branch": "",
  "pullDiagnosticsOn": "both",
  "useBundlerCompose": false,
  "bypassTypechecker": false,
  "rubyExecutablePath": "",
  "indexing": {},
  "erbSupport": true,
  "featureFlags": {},
  "sigOpacityLevel": "1"
}

Reproduction steps

1. Start the Ruby LSP using vscode
2. It will fail
3. Clic "Bundle install" in the error message
4. See unexpected behavior

Code snippet or error message

➜  bundle install
Your Ruby version is 3.3.5, but your Gemfile specified 3.3.7
➜  rbenv versions
  system
  3.2.2
  3.2.3
  3.2.4
* 3.3.5 (set by RBENV_VERSION environment variable)
  3.3.6
  3.3.7
  3.4.1
➜  cat .ruby-version
3.3.7

Seems ruby version is set by RBENV_VERSION and not .ruby-version.
I set up rbenv i .profile which is sourced by .zshrc like this:
eval "$(rbenv init -)".

Everything is working in my normal terminal.

[baelter]

A clean restart solved it. I suspect there might be some issue with have multiple workspaces folders with different ruby versions. I'll reopen if it reappears.

[benlieb]

Having same problem with RBENV_VERSION being set...

Is ruby-lsp doing this?

[benlieb]

Seems to be corresponding to a ruby version being set in my ~/.ruby-version, not my_project/.ruby-version

Does that mean that ruby lsp is executing commands outside of my project directory? How to I ensure that the ruby versions are the same in ruby lsp and my project directory?

[vinistock]

@benlieb the LSP always activates the Ruby environment on the workspace opened in the editor. Are you by any chance opening a parent directory with the Ruby project nested inside?

Do you happen to have any Ruby LSP related settings?

[benlieb]

@vinistock nope, and nope. It's been a minute, but I think I had to change the ruby version in ~/ruby-version for this to work. Pretty frustrating and makes it hard to have multiple projects with different rubies. That said, I still feel very grateful for this free tool. Thank for all the work everyone!

Not really sure what's going on.

[vinistock]

That shouldn't be happening, we always run all version manager integrations in the context of the workspace.

For rbenv, here's where we invoke the activation script which ultimately land here. We always point to the bundleUri (which is the path to the workspace).

If you inspect the logs in the Ruby LSP channel under the Output tab, can you this log where we print the command we're running and where?

If the path to the workspace is correct, it would also be helpful to understand if you get incorrect results even when running that command manually in your shell. If you copy the command and execute it, do you see the right Ruby version being printed? Or only the global one?

[ricksuggs]

@vinistock I'm experiencing a similar issue. I have a workspace with multiple ruby projects, with different ruby versions specified in <project_root>/.ruby-version. I'm using the rbenv version manager. I can see in the Ruby LSP logs where the commands are being executed with the wrong rbenv environment.

Windsurf Version: 1.12.3
VSCode OSS Version: 1.99.3

Ruby LSP Extension Version
0.9.32

Ruby Version Manager
rbenv

In this example:

• project_1 .ruby_version == 3.3.7
• project_2 .ruby_version == 3.4.3

2025-09-03 13:06:15.897 [info] (project_1) Found rbenv executable at /opt/homebrew/bin
2025-09-03 13:06:15.898 [info] (project_1) Running command: `/opt/homebrew/bin/rbenv exec ruby -EUTF-8:UTF-8 '/Users/rsuggs/.windsurf/extensions/shopify.ruby-lsp-0.9.32-universal/activation.rb'` in /Users/rsuggs/projects/project_1 using shell: /bin/zsh
2025-09-03 13:06:16.982 [info] (project_1) Ruby LSP> Skipping composed bundle setup since /Users/rsuggs/projects/project_1/.ruby-lsp/Gemfile.lock already exists and is up to date

2025-09-03 13:06:17.080 [info] (project_1) Ruby LSP> Running bundle install for the composed bundle. This may take a while...
Ruby LSP> Command: (/Users/rsuggs/.rbenv/versions/3.3.7/bin/ruby /Users/rsuggs/.rbenv/versions/3.3.7/bin/bundle _2.6.8_ check || /Users/rsuggs/.rbenv/versions/3.3.7/bin/ruby /Users/rsuggs/.rbenv/versions/3.3.7/bin/bundle _2.6.8_ install) 1>&2

2025-09-03 13:06:17.293 [info] (project_1) The Gemfile's dependencies are satisfied

2025-09-03 13:06:18.406 [info] (project_1) Initializing Ruby LSP v0.26.1 https://github.com/Shopify/ruby-lsp/releases/tag/v0.26.

.......
2025-09-03 13:28:04.341 [info] (project_1) Found rbenv executable at /opt/homebrew/bin
2025-09-03 13:28:04.342 [info] (project_1) Running command: `/opt/homebrew/bin/rbenv exec ruby -EUTF-8:UTF-8 '/Users/me/.windsurf/extensions/shopify.ruby-lsp-0.9.32-universal/activation.rb'` in /Users/me/projects/project_1 using shell: /bin/zsh
2025-09-03 13:28:05.358 [info] (project_1) Ruby LSP> Skipping composed bundle setup since /Users/me/projects/project_1/.ruby-lsp/Gemfile.lock already exists and is up to date

2025-09-03 13:28:05.443 [info] (project_1) Ruby LSP> Running bundle install for the composed bundle. This may take a while...
Ruby LSP> Command: (/Users/me/.rbenv/versions/3.3.7/bin/ruby /Users/me/.rbenv/versions/3.3.7/bin/bundle _2.6.8_ check || /Users/me/.rbenv/versions/3.3.7/bin/ruby /Users/me/.rbenv/versions/3.3.7/bin/bundle _2.6.8_ install) 1>&2

2025-09-03 13:28:05.687 [info] (project_1) The Gemfile's dependencies are satisfied

2025-09-03 13:28:06.836 [info] (project_1) Initializing Ruby LSP v0.26.1 https://github.com/Shopify/ruby-lsp/releases/tag/v0.26.1....
2025-09-03 13:28:06.842 [info] (project_1) Using formatter specified by user: rubocop_internal
2025-09-03 13:28:06.843 [info] (project_1) Auto detected linters: rubocop_internal
2025-09-03 13:28:06.843 [info] (project_1) Detected test library: rails
2025-09-03 13:28:06.843 [info] (project_1) Finished initializing Ruby LSP!
2025-09-03 13:28:06.850 [info] (project_1) [RuboCop] Activating RuboCop LSP addon 1.71.1.

2025-09-03 13:28:07.250 [info] (project_1) [RuboCop] Initialized RuboCop LSP addon 1.71.1.

2025-09-03 13:28:11.853 [info] (project_2) Found rbenv executable at /opt/homebrew/bin
2025-09-03 13:28:11.854 [info] (project_2) Running command: `/opt/homebrew/bin/rbenv exec ruby -EUTF-8:UTF-8 '/Users/me/.windsurf/extensions/shopify.ruby-lsp-0.9.32-universal/activation.rb'` in /Users/me/projects/project_2 using shell: /bin/zsh
2025-09-03 13:28:12.530 [info] (project_2) Ruby LSP> Skipping composed bundle setup since /Users/me/projects/project_2/.ruby-lsp/Gemfile.lock already exists and is up to date

2025-09-03 13:28:12.620 [info] (project_2) Ruby LSP> Running bundle install for the composed bundle. This may take a while...
Ruby LSP> Command: (/Users/me/.rbenv/versions/3.3.7/bin/ruby /Users/me/.rbenv/versions/3.3.7/bin/bundle _2.6.6_ check || /Users/me/.rbenv/versions/3.3.7/bin/ruby /Users/me/.rbenv/versions/3.3.7/bin/bundle _2.6.6_ install) 1>&2

2025-09-03 13:28:12.851 [info] (project_2) Your Ruby version is 3.3.7, but your Gemfile specified 3.4.3

2025-09-03 13:28:13.124 [info] (project_2) Your Ruby version is 3.3.7, but your Gemfile specified 3.4.3

2025-09-03 13:28:13.129 [info] (project_2) Ruby LSP> Running bundle install failed. Trying to re-generate the composed bundle from scratch

2025-09-03 13:28:13.130 [info] (project_2) Ruby LSP> Running bundle install for the composed bundle. This may take a while...
Ruby LSP> Command: (/Users/me/.rbenv/versions/3.3.7/bin/ruby /Users/me/.rbenv/versions/3.3.7/bin/bundle _2.6.6_ check || /Users/me/.rbenv/versions/3.3.7/bin/ruby /Users/me/.rbenv/versions/3.3.7/bin/bundle _2.6.6_ install) 1>&2

2025-09-03 13:28:13.312 [info] (project_2) Your Ruby version is 3.3.7, but your Gemfile specified 3.4.3

2025-09-03 13:28:13.517 [info] (project_2) Your Ruby version is 3.3.7, but your Gemfile specified 3.4.3

2025-09-03 13:28:13.642 [info] (project_2) bundler: failed to load command: ruby-lsp (/Users/me/.rbenv/versions/3.3.7/bin/ruby-lsp)

2025-09-03 13:28:13.642 [info] (project_2) /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/definition.rb:455:in `validate_ruby!': Your Ruby version is 3.3.7, but your Gemfile specified 3.4.3 (Bundler::RubyVersionMismatch)
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/definition.rb:430:in `validate_runtime!'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler.rb:161:in `setup'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/setup.rb:32:in `block in <top (required)>'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/ui/shell.rb:173:in `with_level'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/ui/shell.rb:119:in `silence'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/setup.rb:32:in `<top (required)>'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/cli/exec.rb:57:in `require_relative'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/cli/exec.rb:57:in `kernel_load'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/cli/exec.rb:23:in `run'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/cli.rb:452:in `exec'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/vendor/thor/lib/thor.rb:538:in `dispatch'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/cli.rb:35:in `dispatch'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/cli.rb:29:in `start'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/exe/bundle:28:in `block in <top (required)>'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /Users/me/.rbenv/versions/3.3.7/lib/ruby/gems/3.3.0/gems/bundler-2.6.6/exe/bundle:20:in `<top (required)>'
	from /Users/me/.rbenv/versions/3.3.7/bin/bundle:25:in `load'
	from /Users/me/.rbenv/versions/3.3.7/bin/bundle:25:in `<main>'

2025-09-03 13:28:13.644 [info] (project_2) [Error - 1:28:13 PM] Server initialization failed.
2025-09-03 13:28:13.644 [info] (project_2)   Message: Pending response rejected since connection got disposed
  Code: -32097 
2025-09-03 13:28:13.644 [info] (project_2) [Error - 1:28:13 PM] Ruby LSP client: couldn't create connection to server.
2025-09-03 13:28:13.644 [info] (project_2)   Message: Pending response rejected since connection got disposed
  Code: -32097 
2025-09-03 13:28:13.644 [error] (project_2) Error starting the server: Pending response rejected since connection got disposed
2025-09-03 13:28:13.645 [info] (project_2) [Error - 1:28:13 PM] Server process exited with code 1.

[benlieb]

I never did find a fix for this

[skuroki]

Same problem occured.

Your Ruby version is 3.3.5, but your Gemfile specified 3.3.6

version: 1.103.2
commit: 6f17636121051a53c88d3e605c491d22af2ba755
date: 2025-08-20T16:45:34.255Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Darwin arm64 24.6.0

Ruby LSP 0.9.32
rbenv

[navels]

the LSP always activates the Ruby environment on the workspace opened in the editor. Are you by any chance opening a parent directory with the Ruby project nested inside?

Aha this was my problem, thanks!

[benlieb]

@benlieb the LSP always activates the Ruby environment on the workspace opened in the editor. Are you by any chance opening a parent directory with the Ruby project nested inside?

Aha this was my problem, thanks!

I don't think so:

[navels]

@benlieb I'd be curious to see your Ruby LSP extension logs when you encounter this problem