Ruby LSP client: couldn't create connection to server #2936
Comments
itinsley
added
bug
|
👋 Can you share the output of this when run on the terminal: |
|
Also getting this as of today. Output of the above: |
|
I got permission denied... not sure if the I'm happy to start again from scratch if there's a way to do this. |
|
Absolutely the same issue got today Before addon version update, just on Friday it was working well |
|
I set launcher feature in settings.json to false and now it started successfully We should blame this #2914 |
|
@ske7 thank you for reporting. We're doing a gradual rollout of the Launcher feature to 5% of users but it looks like there may be some problems. For the others in this thread experience errors, please try the above solution of disabling |
|
I tried these changes and still get:
|
|
Also, if you receive an error like this: Turn off the launcher feature flag: "rubyLsp.featureFlags": {
"launcher": false,
} |
|
Any progress on this? As I said before, is there anything in my setup which is likely to cause the problem? Should I try again without ASDF or brew or zsh? Thanks! |
|
Unfortunately, two separate things got mixed into this same issue. The launcher mode issues are not related to the original author's problem, so please report any of those issues here #2977. @itinsley concerning your problem, do you happen to have any Bundler settings (either user or project level)? Any ASDF customizations? |
|
I'm getting the same error on Mac OS 15.1.1 with Error: I also tried to define a custom command: {
"rubyLsp.featureFlags": {
"all": true,
"launcher": false
},
"rubyLsp.formatter": "rubocop",
"rubyLsp.addonSettings": {},
"rdbg.rubyVersionManager": "asdf",
"rubyLsp.customRubyCommand": "asdf exec ruby"
}The VS Code output: Running command: `. /opt/homebrew/opt/asdf/libexec/asdf.sh && asdf exec ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM::YJIT), version: RUBY_VERSION, gemPath: Gem.path }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")'` in /Users/david/projects/su-backend using shell: /opt/homebrew/bin/zsh
2024-12-16 14:21:39.894 [info] No preset version installed for command ruby-lsp
Please install a version by running one of the following:
asdf install ruby 3.3.6
or add one of the following versions in your config file at /Users/david/.tool-versions
2024-12-16 14:21:39.905 [info] (su-backend) ruby 2.7.5It ignores my local settings while loading the RubyLSP |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Ruby LSP Information
Ruby LSP Information
VS Code Version
1.95.3
Ruby LSP Extension Version
0.8.14
Ruby LSP Server Version
Unknown
Ruby LSP Addons
Ruby Version
3.3.5
Ruby Version Manager
asdf
Installed Extensions
Click to expand
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": "auto" }, "customRubyCommand": "", "formatter": "auto", "linters": null, "bundleGemfile": "", "testTimeout": 30, "branch": "", "pullDiagnosticsOn": "both", "useBundlerCompose": false, "bypassTypechecker": false, "rubyExecutablePath": "", "indexing": {}, "erbSupport": true, "useLauncher": false, "featureFlags": {} }Reproduction steps
Other Info
FWIW I have the following in
./zshrcexport RUBY_CONFIGURE_OPTS="--with-openssl-dir=$(brew --prefix [email protected])" . $(brew --prefix)/opt/asdf/libexec/asdf.shNo .ruby-lsp folder
There is no
.ruby-lspfile or folderStandard Env?
Is there a standard favourable full dev environment settings to follow for a Mac? i.e. shell script/installer/version manager etc
The text was updated successfully, but these errors were encountered: