-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[WINDOWS] Most LSPs give error: "Cannot read LSP message header" #12013
Comments
you might not installed lsp from the log? |
The associated LSP's (should) automatically get installed when installing a language extension. I'd like to note that I do not think that this is the actual problem because Zed does install the appropiate LSP, however I am facing errors like: "cannot read LSP message headers", for most languages. |
I am also having this issue with a fresh build, something changed recently that's causing this. |
I think I found the problem, however I am unsure what file provides the dir. Through my own debugging and in the log in your issue, these are the paths where the module "is not found" From your log: From my log: I have verified the file does exist there but as you can see from the logs, we have this Also printing from
|
Same error here. |
same issue here, any fix yet? |
did you atleast try what beans42 said? |
well, i did change the tailwind and emmet like said @beans42, but the emmet doesnt work, perhaps it has a different path? also i couldnt find async fetch_server_binary and get_cached_server_binary one for the emmet, so i only change the const SERVER_PATH: for the emmet like so : |
well if its different you'll have to do it a bit different, but the logic stays the same. so you can change and write the code yourself or wait for someone else to do so. |
Well, I noticed the same error in tailwind... And it seems to me that the problem is because powershell spits out it's greeting message to standard output, which then confuses the LSP ??? Indeed, when i change line 28 in tailwind.rs to: basically adding "-nologo" parameter, the error is gone from the logs... |
I'm facing the same issue, however, I got it fixed for tailwind in #17741 |
I'm having the same issue on latest build. |
Hi, I was having the same error with several LSPs. For example, when Zed tried to start a new LSP for Svelte, it threw the following error:
The problem is that in the args, Zed somehow adds a slash at the beginning, letting Windows take that slash as the root of the working directory, leaving the result as I:\C:\ in my case. The workaround until a solid one arrives, is as follows: Old:
New:
Now, the log prints the following:
As a result, Svelte suggestions/imports and Emmet inside .svelte files works perfectly. I'm posting this comment because it worked for me and I'll be glad if it helps anyone else. I know this is a crappy solution, but at least, the extensions are working on Windows. If anyone has another solution, I would be happy to see it. |
Check for existing issues
Describe the bug / provide steps to reproduce it
Don't know, I just did compile to Windows and all suddenly most LSPs gave this error.
Environment
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.The text was updated successfully, but these errors were encountered: