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

Don't send info output to stderr #1341

Open
clason opened this issue Jan 9, 2025 · 3 comments
Open

Don't send info output to stderr #1341

clason opened this issue Jan 9, 2025 · 3 comments

Comments

@clason
Copy link

clason commented Jan 9, 2025

LanguageServer.jl (and some of its dependent packages) send (all?!) info output (such as the timing summary or the packages loaded from cache) to stderr, which leads to quickly ballooning log files in clients such as Neovim since these messages are treated as actual errors.

As these are not error messages, they should be emitted accordingly (stdout, or ideally as actual LSP notifications).

@davidanthoff
Copy link
Member

We can't send anything to stdout as that is used for the actual JSONRPC commutation.

Also, stderr seems exactly the right place to send (non error) log output to? In VS Code for example that ends up in the log output view for the LS which is super helpful. I guess you could run the Ls with a different log level if you don't want to see these messages?

@clason
Copy link
Author

clason commented Jan 9, 2025

I guess you could run the Ls with a different log level if you don't want to see these messages?

That is exactly what I'm doing; I don't expect to see these messages with a log level set to "ERROR". (No other server sends "INFO" messages by default.)

(Obviously, you could say the server is still WIP, so any use would be testing and debugging, but...)

@clason
Copy link
Author

clason commented Jan 9, 2025

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

2 participants