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

Output error stream when developing language server #1019

Closed
datho7561 opened this issue Apr 20, 2021 · 0 comments · Fixed by #1020 or enxio/lsp4xml#126
Closed

Output error stream when developing language server #1019

datho7561 opened this issue Apr 20, 2021 · 0 comments · Fixed by #1020 or enxio/lsp4xml#126
Assignees
Milestone

Comments

@datho7561
Copy link
Contributor

Set up the default error stream to be output somewhere when developing the server. This allows the developer to access the Exception traces that happen before the language client connects to the server.

In particular, this would be very helpful when trying to debug the native image of the server. Crashes can occur during the initialization request, since all the classes that form the initialization request must be registered for reflection in order to successfully send the request.

@datho7561 datho7561 self-assigned this Apr 20, 2021
datho7561 added a commit to datho7561/lemminx that referenced this issue Apr 20, 2021
If the environment variable `LEMMINX_DEBUG` is set,
then Java's errors will not be disconnected from standard error.

Closes eclipse-lemminx#1019

Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561 added a commit that referenced this issue Apr 21, 2021
If the environment variable `LEMMINX_DEBUG` is set,
then Java's errors will not be disconnected from standard error.

Closes #1019

Signed-off-by: David Thompson <davthomp@redhat.com>
@datho7561 datho7561 added this to the 0.17.0 milestone Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant