-
Notifications
You must be signed in to change notification settings - Fork 58
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
fix: don't log same BadLocationException excessively #1083
Conversation
I prefer to have the exceptions in the log if the error happens. Otherwise the user will still miss some feature and will not know why. Is the error such a problem that we would like to hide it? |
I guess the problem is the amount of exceptions being logged repetitively and since it has been reported several times it seems to be an annoyance to users. Also in the error log view there is the option "Activate on new error" which would frequently re-activate that view. Maybe we can just lower the severity to warning or info instead of error? |
What about counting exceptions and only log the first three unless in debug mode? I think that is a good compromise between informing the user and not bothering him |
@rubenporras ok, please check my update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
The goal of this PR is to address #899 , #536 and #203 by logging BadLocationExceptions in LSPDiagnosticsToMarkers and SymbolsLabelProvider only when
Platform.getDebugOption("org.eclipse.lsp4e/debug")
is set to true.