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

Unusual tsserver error output on new install #676

Open
jcuffe opened this issue Mar 7, 2023 · 3 comments
Open

Unusual tsserver error output on new install #676

jcuffe opened this issue Mar 7, 2023 · 3 comments

Comments

@jcuffe
Copy link

jcuffe commented Mar 7, 2023

After an unfortunate machine wipe, I recently reinstalled kak, kak-lsp, and all of their dependencies, and kak-lsp is show extremely frequent errors that I haven't seen in the past and am unsure how to diagnose. This could definitely be an issue with tsserver, but I wanted to see if anyone had encountered it in this context. The numbers in this error frequently change, but the discrepancy is always 1:
image

Here is my config for javascript lang:

[language.tsx]
filetypes = ["typescript", "javascript"]
# roots = ["tsconfig.json", "package.json", ".git"]
roots = [".git"]
command = "typescript-language-server"
args = ["--stdio"]
# settings_section = "initializationOptions"
# [language.tsx.settings.initializationOptions]
# maxTsServerMemory = 2048
@jcuffe jcuffe changed the title Unusual error output on new install Unusual tsserver error output on new install Mar 7, 2023
@sidkshatriya
Copy link
Contributor

Typically when some language server fails you need to check if the failure is due to kak-lsp or the language server.

So lets say your ts project is in /home/abc/myproject.

Do the following

$ cd /home/abc/myproject
$ typescript-language-server --stdio

Basically you are just invoking the language server manually. Usually if something is extremely wrong with the LSP you will get an error right away on invoking it.

When that happens you know that kak-lsp is not at fault, it is the language server itself.

@krobelus
Copy link
Member

krobelus commented Mar 8, 2023

This looks like a typescript-language-server issue. Can you edit your toml config to add --log-level=4, reproduce the issue and report that upstream?
A kak-lsp log would also contain the same information but it would harder to read for them presumably

@jcuffe
Copy link
Author

jcuffe commented Mar 8, 2023

Thank you both for your suggestions!

@sidkshatriya Running the language server directly from command line showed no issues, which aligns with my experience as this error typically occurs after a few minutes of editing.

@krobelus I've gotten the language server running with --log-level=4 and will see what I can find in those logs.

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

3 participants