-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request textDocument/documentSymbol failed #820
Comments
Also having the same issue on 2.5.0 with the following VScode setup:
|
In the meantime, grab the 2.4.0 VSIX from https://github.com/godotengine/godot-vscode-plugin/releases/tag/2.4.0 and install it. |
It may be worth noting (at least, in my case) - there doesn't seem to be any actual impact, other than the warning dialog popping up in the corner any time text is edited. Everything seems to be working so far for me. |
I can't replicate this on either win10 or debian using Godot 4.4 stable. Can somebody share a minimum reproduction or something? |
I have this error, but it isn't consistent across all my projects. One smaller project runs fine, while another larger project has the issue. Using same user configs and settings in both, and both are on same machine, windows 11. Also worth noting: This appears in my converted projects, not ones created in 4.4 as far as I can see.
|
I tried creating a new Godot 4.4 project, nothing inside it except a test.tscn file with a simple Node and a test.gd script. First, the error didn't appear when opening and editing the test.gd file. Here is the full code for this project
Inside Do you need a repo with that test project? It really is empty appart from this test scene. |
@devzenfr That replicates it immediately, thanks. Give me a little time to look into this. |
Godot version
4.4.stable
VS Code version
1.98.1
Godot Tools VS Code extension version
2.5.0
System information
MacOS Sequoia 15.2
Issue description
Since upgrading to Godot 4.4 and plugin version 2.5.0, opening a gdscript file displays the following error
The error appeared right after updating plugin to 2.5.0.
Steps to reproduce
The text was updated successfully, but these errors were encountered: