VLS fails with no clear reason on vscode #236
Labels
unconfirmed
Unconfirmed bug
Comments
|
Have you tried this with other projects? There seems to be an issue with the Meson build in iagno: You should know that VLS doesn't yet support |
|
I have tried with various other Vala projects but it fails with #220, also I don't see what is wrong with the Meson build as it builds just fine. Anything specific I should look at ? Is the flatpak-builder integration needed at all? vls just needs to be run inside the sandbox and that should be good enough I guess. |
|
One thing you can do is enable "Debug Mode" and rerun VLS, then give me the output log from that. Also, please do this on 0.48.5 now. If it is still a problem I'll look into it. |
|
I didn't get any more information with the debug mode enabled |
|
Are you sure debug mode was enabled and you restarted VLS / VSCode? You should at least see a bunch of vls-DEBUG messages related to configuring the project. |
|
Sry, I meet the same problem. Environment：MacOS BigSur 11.5.2, VS Code 1.71.2, vala 0.56.3, vala-language-server 0.48.5, vala vscode extension v1.0.8. |
|
I'm having a similar issue, The repo is a private one, but the error looks to be similar to the one that's been seen above (from VSCode). I tried Hopefully it helps? |
|
I'm having the exact same issue. No matter what I try, some version of this issue eventually shows up every time i reload vala-language-server: It tends to fail with several textDocument/* requests, not just documentSymbol. Otherwise, all of the error messages look the same, down to the line numbers I am running Fedora 37. This issue seems to persist regardless of which repository i open, and regardless of which vscode extensions i enable (besides vala language support) |
|
I'm having the same issue as of this morning, also on Fedora 37. |
|
/EDIT/ Chiming in to say that I have the same problem. Playing around with GTK4. I have attached my source file if it is of any help: gtk_helloworld.zip It is compiled using "valac --pkg gtk4 -X -mwindows gtk_helloworld.vala" Software To reproduce And this is what happens when you then start typing: |
|
Compiled from source and now I get this when opening a file in vs-code: The language server does not immediately crash anymore, and provides suggestions after periods, though I assume it's hampered somewhat because "The name 'Gtk' does not exist in the context of 'main'". An instant way to make the server crash, is to add "using Gtk;" (which also can't be found) at the top of the file, and then enter a period after "Gtk", and before the semicolon. vs-code will show many boxes in rapid succession immediately upon doing so, informing you that the server has crashed, until it stops upon hitting the five-times crash limit. |
|
Can anybody reproduce this issue on 0.48.7? |
|
I was able to replicate @Martin-Niemann 's crash on 0.48.7 I also had to manually build VLS, since Fedora's repository is still on 0.48.5, which still crashes instantly. |
|
For me it's crashing with 48.5 as well as 48.7. An almost instant crash every time I open VS Code. |
|
@DanDankRaft @SubhadeepJasu can you provide a way to reproduce this issue on 0.48.7? |
|
@Prince781 (This set of errors repeats several times until declaring that the server "crashed 5 times in the last 3 minutes. The server will not be restarted") |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
Software
OS and version (e.g. Ubuntu 20.04): VLS from the flatpak sdk
Code editor (e.g. VSCode): VScode
Vala Language Server (e.g. git commit, or PPA/AUR version): 0.48.4
Vala version (
valac --version): 0.55.90.11-90d58To Reproduce
Source code repo: Clocks https://gitlab.gnome.org/GNOME/iagno with a modified flatpak manifest as explained in https://github.com/flathub/org.freedesktop.Sdk.Extension.vala#usage in order to make flatpak-vscode to modify VLS for it to run inside the sandbox instead of the host
That is what I get in the output tab, and nothing seems to work at all
The text was updated successfully, but these errors were encountered: