Issues with handling LSP servers #33740
Replies: 6 comments
|
Hey, the missing URI should be fixed as of #25264 |
|
For a bit of context, last Preview (0.175.x) includes significant changes to how we spawn language servers. I think this might be the cause of problems outlined in "LSP Not Shutting Down Properly When Closing Workspaces", but given the timeline (this change is pretty recent) I don't think it's necessarily related to "Missing File Events or LSP Not Starting Properly" |
|
Acording to xhyrom/zed-discord-presence#35 (comment) the problem with missing file events (unable to detect project files) also occurs on 0.176.1 |
|
As-is I don't think there's enough here to be actionable. It sounds like you're describing a number of issues you're having with Zed (LSPs staying running after workspace files are closed, LSPs not being notified of file events as expected, windows unzip errors). But none of them are actually actionable. If you have steps to reproduce for any of these please open a issue scoped to a particular issue with steps to reproduce. I'm going to migrate this into a discussion so this can be investigated further. |
|
Thanks for reaching out. We want to better support our community, and the best way for us to do that is through our official Discord. The team is active there and happy to help. We’re closing the “Help and General Q&A” category on GitHub Discussions and directing all support questions to Discord going forward. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
LSP Fails to Start Due to Missing Root URI
Users of my Zed extension, Discord Presence, have reported "Failed to get root URI" errors. This happens because the extension relies on the root URI to determine the workspace folder name. A recent PR #25344 might have already addressed this.
Missing File Events or LSP Not Starting Properly
Based on xhyrom/zed-discord-presence#20 and xhyrom/zed-discord-presence#31, Zed sometimes fails to detect files correctly. As noted in this comment, the LSP doesn’t always start when it should. However, switching to a completely different file and then back to the original one seems to trigger the LSP.
LSP Not Shutting Down Properly When Closing Workspaces
There’s also an issue with shutting down the LSP when closing a workspace. For example, if Zed's settings.json is opened and then closed, the LSP remains active. This results in settings.json still appearing as the active file, even though it’s no longer open. This issue also occasionally occurs when closing Zed entirely.
Unzipping Issues on Windows
On Windows, Zed sometimes fails to download and extract files, showing the error:
"failed to download file: failed to unzip".
This issue occurs randomly, similar to zed-industries/zed#22815.
Zed Version and System Specs
Zed: v0.174.6, v0.173.10, v0.16.1
Operating system: Arch Linux, Void Linux and Windows (unzipping issue)
All reactions