Ruby Solargraph stuck on "mapping workspace" loop
See original GitHub issueDescribe the bug When starting the Ruby Solargraph language server, the status bar shows that it is stuck on a “Mapping workspace… Mapping complete” loop and never activates.
The LSP log panel shows that Solargraph is restarted repeatedly:
ruby: Solargraph is listening on stdio PID=95791
ruby: Solargraph is listening on stdio PID=95827
ruby: Solargraph is listening on stdio PID=95887
ruby: [WARN] Empty cache for bundler 1.17.2. Reloading
ruby: Solargraph is listening on stdio PID=95926
ruby: Solargraph is listening on stdio PID=95962
ruby: [WARN] Empty cache for sixarm_ruby_unaccent 1.2.0. Reloading
ruby: Solargraph is listening on stdio PID=95998
ruby: Solargraph is listening on stdio PID=96034
ruby: Solargraph is listening on stdio PID=96070
ruby: Solargraph is listening on stdio PID=96106
ruby: Solargraph is listening on stdio PID=96142
ruby: Solargraph is listening on stdio PID=96178
ruby: Solargraph is listening on stdio PID=96214
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96250
ruby: Solargraph is listening on stdio PID=96286
ruby: Solargraph is listening on stdio PID=96322
ruby: Solargraph is listening on stdio PID=96358
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96394
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96430
ruby: Solargraph is listening on stdio PID=96466
ruby: Solargraph is listening on stdio PID=96502
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96538
ruby: Solargraph is listening on stdio PID=96575
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96611
ruby: Solargraph is listening on stdio PID=96647
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96683
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96720
ruby: Solargraph is listening on stdio PID=96757
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96793
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96829
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96865
ruby: Solargraph is listening on stdio PID=96901
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=96937
ruby: Solargraph is listening on stdio PID=96973
ruby: Solargraph is listening on stdio PID=97009
ruby: Solargraph is listening on stdio PID=97045
ruby: Solargraph is listening on stdio PID=97082
ruby: Solargraph is listening on stdio PID=97118
ruby: Solargraph is listening on stdio PID=97154
ruby: [WARN] Discarding client response to unrecognized message 1
ruby: Solargraph is listening on stdio PID=97190
ruby: Solargraph is listening on stdio PID=97226
ruby: Solargraph is listening on stdio PID=97262
ruby: Solargraph is listening on stdio PID=97298
To Reproduce Steps to reproduce the behavior:
- Open a folder with a Rails project in it
- Enable the Solargraph LSP server through
LSP: Enable Language Server Globally>Ruby - The server is stuck on a “mapping workspace” loop
Expected behavior The server is not stuck on a loop and activates eventually.
Screenshots Here is a screen recording of the log panel and the status bar
Environment (please complete the following information):
- OS: Ubuntu 20.04.3 LTS
- Sublime Text version: 4113
- LSP version: 1.10.1
- Language servers used: LSP-pyright, LSP-bash, LSP-css, LSP-html, LSP-json, LSP-typescript
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Scanning Workspaces - Solargraph
Scanning Workspaces. The solargraph executable includes a scan command to look for code in your workspace that Solargraph can't parse or map.
Read more >Core - LSP Mode - LSP support for Emacs
List of functions to be called after a Language Server has been initialized for a new workspace. lsp-after-open-hook #. Type: hook. Default: nil....
Read more >Ruby vs. Python comes down to the for loop | Hacker News
I'm not sure where the author is getting this. It is certainly possible, as shown, but definitely not common to implement `select` or...
Read more >Untitled
Msi v220 review, Steinigke, Tabriz street map, Lenco finance walker louisiana, ... Pentax 24-35mm lens, Berlingo dangel 4x4 occasion, For loop in razor, ......
Read more >kYw - ALBA.Net
Ayzha khan, Lagu d'pas4 buku harian, Diyawanna oya map, Maramag bukidnon festival, ... Opel agila wit 2005, Urbs celeberrima, Happy thanksgiving loops!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@timfjord Gem version 0.43.2 has an update for your issue. See castwide/solargraph#461
@jamesWalker55 I’m afraid I don’t know enough about Sublime to help troubleshoot effectively, but I’ll help however I can and address any problems I’m able to reproduce. In VS Code, I would recommend setting
solargraph.logLeveltodebugand checking the console output (i.e., stderr), but I don’t know what the equivalent would be in Sublime.In this client, and if I understand solargraph correctly, you should be able to set “logLevel”: “debug” in the “initializationOptions” dict.