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

LSP server no response after receiving an early workspace/didChangeConfiguration notification #434

Open
Zjl37 opened this issue Feb 18, 2024 · 0 comments

Comments

@Zjl37
Copy link

Zjl37 commented Feb 18, 2024

  • Component:
    • LSP (used with other editor)
  • LSP version: Version: 0.12.1, commit 1928d88ff8bc3e178ad098146bec252751383a48 (Typst version 0.10.0)
  • OS version and name: Arch Linux, up to date
  • ✅ I am on the latest stable version of the extension/LSP.
  • ✅ I have searched the issues of this repo and believe that this is not a duplicate.

Issue

Typst-lsp does not give any responses at all after receiving an early workspace/didChangeConfiguration notification, though the "settings" param is empty. This causes it fail to work with Emacs's eglot. I have asked eglot's developer: joaotavora/eglot#1363 and they thought it's server's bug.

As long as I configure the client not to send workspace/didChangeConfiguration after connection, the server would work properly.

The above eglot issue contains a minimal recipe of reproduction steps.

Logs

https://gist.github.com/Zjl37/d506c225bce175e584a78d47e0dbecab

Note there are many "timed-out request" message near the bottom of the log, and that the workspace/didChangeConfiguration notification is sent to server before server registers this capability.

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

1 participant