-
Notifications
You must be signed in to change notification settings - Fork 16
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
Failing with dbt #22
Comments
Hi, Thanks for your report. Based on the error message, it seems that it received unexpected data from dbt-language-server (cannot parse as json-rpc header). It would help a lot if you can post the output of the language server here. You may do it in this way:
(I tried to reproduce this locally but unfortunately cannot get dbt-language-server working (constantly getting an "invalid_type" type error...).. ) |
Thanks @blahgeek ! Here is my emacs setup for dbt: fivetran/dbt-language-server#1426 (comment) I can send you those files, but they contain some semi-private information. Can I email you? My email is on my profile. |
Hi @egh , At the end of your
These "Running server on ..." lines are the ones that causes the issue. The dbt language server should not output these contents to stdout according to lsp spec (it should only contains "Content-Length: xxx" followed by json objects). So I think maybe you should report to dbt-language-server project about this bug. (Though as I said, I personally cannot reproduce this, so I'm not sure why or when it happens) On the other hand, emacs-lsp-booster could try to tolerate this kind of error and try to recover. I think that's how lsp-mode itself does, which explains why you don't have this issue without emacs-lsp-booster enabled. I will do this later. |
Hi @blahgeek , Thank you so much for looking into this! I will file an upstream bug. |
Hi,
I'm trying this out with https://github.com/fivetran/dbt-language-server but I'm getting the following error. If I disable
emacs-lsp-booster
things work fine. Let me know what info I can provide. Thanks!The text was updated successfully, but these errors were encountered: