Boot loop when `.ruby-version` doesn't match in `Gemfile.lock`

[Earlopain]

Description

Ruby LSP Information

Details

Ruby LSP Information

VS Code Version

1.94.0

Ruby LSP Extension Version

0.8.4

Ruby LSP Server Version

0.19.2

Ruby LSP Addons

Ruby Version

3.3.5

Ruby Version Manager

rbenv

Installed Extensions

Click to expand

• gitlens (15.6.0)
• go (0.42.1)
• vscode-rdbg (0.2.2)
• remote-containers (0.388.0)
• material-icon-theme (5.11.1)
• vscode-yaml (1.15.0)
• ruby-lsp (0.8.4)
• sorbet-vscode-extension (0.3.37)
• vscode-wakatime (24.6.2)

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": "none",
  "linters": null,
  "bundleGemfile": "",
  "testTimeout": 30,
  "branch": "",
  "pullDiagnosticsOn": "both",
  "useBundlerCompose": false,
  "bypassTypechecker": false,
  "rubyExecutablePath": "",
  "indexing": {},
  "erbSupport": true
}

Reproduction steps

# .ruby-version
3.3.5

# Gemfile
source "https://rubygems.org"

ruby file: ".ruby-version"

# Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:

PLATFORMS
  ruby
  x86_64-linux

DEPENDENCIES

RUBY VERSION
   ruby 3.3.4p94

BUNDLED WITH
   2.5.20

It successfully does its initial indexing but exits shortly after to restart, going back to indexing, exiting again, etc. You get the idea. There are no meaningful log lines in the extension output window.

This is cleary the error of whoever let those files get out of sync like that but I would expect the lsp to show a clear error message in that case.