Crashing on startup when connecting to the database #521
Labels
bug
Something isn't working
Comments
|
Attempting the stop the Ruby LSP server raises;
Which suggest the LSP is a weird locked state. |
|
There is a somewhat suspicious |
|
Turned on LSP message debugging... I think there's something wrong with CodeLens. In the space of a minute, it sent 300 CodeLens requests which seems, excessive. Truncated log ... |
|
I might try more things. This could very well be "my setup is broken somehow" but it definitely feels weird how the language server just stops. I wonder if the Rails Add on is having a bad time. |
|
Fwiw I'm seeing similar issues with my setup this morning. |
|
As a first step, please try downgrade to the previous VS Code release (find Ruby LSP in the extensions panel then Right Click-> Install Specific Version -> 0.8.12) and report if you're still seeing the issue. |
|
Also please check if you see this on a plain Ruby repo, or if it only happens for a Rails app. |
Did that. Still broken
Will do, but that'll be tomorrow. Bit late here now in Australia 😄 🇦🇺 |
On the terminal, if you run |
andyw8
changed the title
|
I've renamed the issue to better reflect what's currently known. |
|
Hi, @andyw8 . I have the same problem and tried what you said here:
It failed, really didn't connect to the db. That's because I don't use rails natively while developing. I do all my testing inside a docker container. I don't know if this helpful for you somehow. |
|
Thank you, that helps. #517 should help. |
|
We have merged a fix. To help us verify before shipping in the next release, please try tempoarily pointing your app's
(then run bundle and reload your editor) |
|
(I should move this issue to the |
|
@andyw8 Can confirm that fixed my problem! Also nicer error message too! I'm happy for this issue to be closed off. Before: Couldn't save files 😢 After: Can save files 🥳 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Ruby LSP Information
Suddenly since yesterday, when I save a ruby file it brings up the "Ruby LSP is formatting the document... " wait message and never actually completes. I think this is more related to the LSP server crashing but I can't prove it yet.
Downgrading the extension to v0.18.2 removes the "problem" so there's something going on. EDIT - It did not remove the problem.I need to actually do work so I'm keeping it at this version and when I get more time (shortly) I'll update this issue with all the diagnostics and debug information I can.
Raising this issue incase anyone else has strange crashes in v0.18.3
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": "rbenv" }, "customRubyCommand": "", "formatter": "auto", "linters": null, "bundleGemfile": "", "testTimeout": 30, "branch": "", "pullDiagnosticsOn": "both", "useBundlerCompose": false, "bypassTypechecker": false, "rubyExecutablePath": "", "indexing": {}, "erbSupport": true, "useLauncher": false, "featureFlags": {} }Reproduction steps
TBA
The text was updated successfully, but these errors were encountered: