Do not log debug output on info level #1536
Merged
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
This causes any client to log all output messages twice, one in the official output for example in the editor and the second time in the logs, which can just grow the logs without purpose. We should still be able to print it under debug flag.
adpi2
approved these changes
Jul 29, 2021
ckipp01
approved these changes
Jul 29, 2021
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.
This causes any client to log all output messages twice, one in the official output for example in the editor and the second time in the logs, which can just grow the logs without purpose.
We should still be able to print it under debug flag.
Connected to scalameta/metals#2311
Tested it locally and it works correctly. There is no need for logging all output since everything goes through DAP anyway.