Skip to content
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

Problems with 4.4.dev #35

Closed
1 of 2 tasks
gro-david opened this issue Jan 8, 2025 · 4 comments
Closed
1 of 2 tasks

Problems with 4.4.dev #35

gro-david opened this issue Jan 8, 2025 · 4 comments

Comments

@gro-david
Copy link

I'm submitting a...

  • Bug report.
  • Feature request.

Bug report

I just updated Godot to version 4.4.dev (from the AUR), to be able to use it on Wayland with less problems. Since then the LSP cannot seem to connect, the error from stderr is missing:

This is the output in Zed:

Language server error: gdscript

LSP request timeout
-- stderr--

What is the current behavior?
The LSP does not connect, and fails without errors.

What is the expected behavior?
The LSP should connect without problem.

Tell us the steps to reproduce the bug, and if possible share a minimal demo of the problem.

I have absolutely no idea if this is because of 4.4.dev or something else, up to this point it had beed working without issues. Otherwise just build Godot from the GitHub repo and try it with that. Ideally on Linux.

Feature request

Describe the problem you're trying to solve.

Tell us which solutions you've explored, the solution you would pick, and why you think it would be the best for everyone.

Other

Other information

@moomerman
Copy link
Contributor

@gro-david I've experienced the same thing. Will try and take a look later what is going on but this plugin doesn't do much, it simply passes on the LSP requests to Godot using netcat so can't imagine how we can fix it on this end.

@gro-david
Copy link
Author

Yes you are most probably right. I have found the following issue on the Godot GitHub issue and pull request: godotengine/godot#100950. This addresses it. Should I close this issue then, or should I leave it open so other people can find it?

@moomerman
Copy link
Contributor

Oh great find! Yep, probably worth keeping open for now and close when the next release comes out assuming the fix is in ❤️

@gro-david
Copy link
Author

The PR was closed recently, which in fact did fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants