Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Show message to the user in case of language server starting error
See original GitHub issueStarting a language server via a client.start() can result in an error. Usually the stdout or stderr for the server process contain hints to what the problem could be. In case of such an error while starting the server, the only message displayed to the user is something like:
[Error - 1:33:53 PM] Connection to server got closed. Server will not be restarted.
I wonder if there’s any way to improve the situation and display the stdout/stderr from the server to the user when the language server fails to start. The clientOptions include a errorHandler that can be customized, but that doesn’t seem to help, since when the issue occurs the closed() method does not get any arguments.
Note: I’m not a Typescript / JS developer myself, so there may be something I’m missing.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The handler now allows to return a message that will be presented to the user with a button to open the output channel (which contains stdout)
I think Roberto is talking about a scenario where the server is misconfigured, and fails to start.
At the moment you just get an error saying the server did not start, and eventually reports 5 failures and stops.
Perhaps we could have an option when that point is reached to display whatever the server did emit on stdout/stderr somewhere on the client.