Ignore setTrace requests #5894
Merged
Ignore setTrace requests #5894
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sdedic
added
LSP
dbalek
approved these changes
Jun 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NBLS currently throws
UnsupportedOperationExceptionwhen vscode optionjava.trace.serveris set toverbose'. The LSP client sends asetTrace` notification to the client which was unimplemented.After discusson with @dbalek, I've decided to just trash the reques: log verbosity can be (and is) controlled by
-J-Dnetbeans.console.logger=trueby the vscode extension client and the number of protocol messages that appear in the client's output is quite high already.