-
Notifications
You must be signed in to change notification settings - Fork 93
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
Catch errors from any participants. #946
Comments
datho7561
added a commit
to datho7561/lemminx
that referenced
this issue
Dec 10, 2020
Fixes eclipse-lemminx#946 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/lemminx
that referenced
this issue
Dec 15, 2020
Fixes eclipse-lemminx#946 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/lemminx
that referenced
this issue
Dec 16, 2020
Fixes eclipse-lemminx#946 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/lemminx
that referenced
this issue
Dec 16, 2020
Fixes eclipse-lemminx#946 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/lemminx
that referenced
this issue
Dec 17, 2020
Fixes eclipse-lemminx#946 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/lemminx
that referenced
this issue
Dec 17, 2020
Fixes eclipse-lemminx#946 Signed-off-by: David Thompson <davthomp@redhat.com>
angelozerr
pushed a commit
that referenced
this issue
Dec 17, 2020
Fixes #946 Signed-off-by: David Thompson <davthomp@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All participants like diagnostics, completions, etc loop for each participant and if one of participant throws an error, it breaks the other participants. For diagnostics case it seems that when a participant throw an error, the LSP publishDiagnostics is not traced in the console.
We should try catch each participant and log the error for each participant which throw an error.
For instance I suspect in #945 that there is this problem.
XMLDiagnostics should look like this:
It should be fine to:
The text was updated successfully, but these errors were encountered: