<class:RunnerClient>': superclass mismatch for class IncompleteMessageError (TypeError) #524
Comments
|
Thank you for the bug report! Something is quite odd here. The issue seems to be that we're requiring more than one version of the Rails add-on. If you check the output, we printed that we were activating version v0.3.25, but the backtrace is pointing to v0.3.18 - which is most certainly where the superclass mismatch error is coming from. Can you please share these to help us diagnose?
Also, I see that you're on an old version of the VS Code extension. Can you please upgrade to the latest and let us know if the problem persists? |
|
Hi Vinicius,
Thanks for your help. I’m using `rvm` as my version manager, and here is the snippet for the rubylsp configuration from my settings.json:
```
"rubyLsp.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
},
"rubyLsp.featuresConfiguration": {
},
"rubyLsp.linters": [],
"rubyLsp.rubyVersionManager": {
"identifier": "rvm"
},
```
Also, I believe I have the latest extension installed from the https://open-vsx.org
***@***.***
Thanks!
Kayvon
From: Vinicius Stock ***@***.***>
Sent: Monday, November 18, 2024 1:57 PM
To: Shopify/ruby-lsp-rails ***@***.***>
Cc: Kayvon Shahir ***@***.***>; Author ***@***.***>
Subject: Re: [Shopify/ruby-lsp-rails] <class:RunnerClient>': superclass mismatch for class IncompleteMessageError (TypeError) (Issue #524)
CAUTION: External Email. Proceed Responsibly.
Thank you for the bug report! Something is quite odd here. The issue seems to be that we're requiring more than one version of the Rails add-on. If you check the output, we printed that we were activating version v0.3.25, but the backtrace is pointing to v0.3.18 - which is most certainly where the superclass mismatch error is coming from.
Can you please share these to help us diagnose?
1. What version manager are you using?
2. Do you have any Ruby LSP related settings in the editor?
Also, I see that you're on an old version of the VS Code extension. Can you please upgrade to the latest and let us know if the problem persists?
—
Reply to this email directly, view it on GitHub<#524 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFRA7QCEZUNJJO64SC3NHEL2BJPD3AVCNFSM6AAAAABRUTSBISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBUGIYTIOJTGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
|
We print the activated Ruby environment to the We've seen this type of issues before and it's typically because something is setting |
|
I was able to find this snippet in the log in regard to the Bundle file:
***@***.***
Here is also from the log showing some output in regards to ruby-lsp-rails initialization:
***@***.***
From: Vinicius Stock ***@***.***>
Sent: Tuesday, November 19, 2024 11:36 AM
To: Shopify/ruby-lsp-rails ***@***.***>
Cc: Kayvon Shahir ***@***.***>; Author ***@***.***>
Subject: Re: [Shopify/ruby-lsp-rails] <class:RunnerClient>': superclass mismatch for class IncompleteMessageError (TypeError) (Issue #524)
CAUTION: External Email. Proceed Responsibly.
We print the activated Ruby environment to the Output tab under the Ruby LSP channel. Can you please check if the activated environment includes BUNDLE_GEMFILE by any chance?
We've seen this type of issues before and it's typically because something is setting BUNDLE_GEMFILE and making the Ruby LSP skip its composed bundle logic, which then doesn't setup Bundler properly and results in requiring the wrong add-on versions. We need to understand what is causing it for your setup.
—
Reply to this email directly, view it on GitHub<#524 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFRA7QGRU636BT7B5WHVOVT2BOHLRAVCNFSM6AAAAABRUTSBISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGU4DQNBRGM>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Hi, I'm encountering this error during the boot-up process of the Rails LSP server. I am running Ruby 3.1.2, and environment spec are:
RUBY_VERSION=ruby-3.1.2
Ruby Client: Vscode extension: Ruby LSP
v0.7.14
Gemfile.lock
Error:
The text was updated successfully, but these errors were encountered: