search

godotengine / godot-vscode-plugin

Godot development tools for VSCode
MIT License
1.57k stars 168 forks source link

Error in Cursor IDE: Request workspace/symbol failed. Message: Method not found: symbol #701

Closed PLyczkowski closed 3 weeks ago

PLyczkowski commented 2 months ago

Godot version

4.3 stable

VS Code version

Cursor

Godot Tools VS Code extension version

2.1.0

System information

Windows 10

Issue description

Cursor IDE, which is a fork of VSCode, throws this error when trying to do anything: Request workspace/symbol failed. Message: Method not found: symbol Code: -32601 Hard to tell if it's a Cursor bug or the extension.

Steps to reproduce

Try Cursor with the extension, try to do anything.

PLyczkowski commented 2 months ago

No longer happens after updating Cursor

PLyczkowski commented 2 months ago

Oops, disregard that, I tested wrong. The chat window works, the instructions window does not: image

DaelonSuzuka commented 1 month ago

This is either a problem with Cursor requesting a non-standard method, or the Godot Language Server not correctly implementing a required method. This extension has no control over either of those. You could open an issue at https://github.com/godotengine/godot.

andyfangaf commented 1 month ago

Same issue here with Cursor, it's very annoying as it pops up all the time. Is there at least a way to hide it from showing? CleanShot 2024-09-23 at 00 51 08@2x

DaelonSuzuka commented 1 month ago

Can somebody try installing this development build and seeing if that fixes the problem?

Cursor is using the workspace/symbol request to get info about symbols in the file and (I assume) feeding that info to its LLM. I can't actually implement the workspace/symbol method in the Godot engine, but hopefully this build stops the annoying error.

dannypostma commented 4 weeks ago

This solved the issue for me @DaelonSuzuka, ty!

PLyczkowski commented 4 weeks ago

Can somebody try installing this development build and seeing if that fixes the problem?

Cursor is using the workspace/symbol request to get info about symbols in the file and (I assume) feeding that info to its LLM. I can't actually implement the workspace/symbol method in the Godot engine, but hopefully this build stops the annoying error.

Can confirm this solves the problem 👍

DaelonSuzuka commented 3 weeks ago

The fix for this issue was just published in 2.3.0! Thanks for testing the build for me @dannypostma and @PLyczkowski!