Skip to content

Conversation

jasonmalinowski
Copy link
Member

@jasonmalinowski jasonmalinowski commented May 12, 2025

10.0.0-next.15 brings full support for LogOutputChannels which cleans up the logging of severities and timestamps. Otherwise we end up with confusing duplicate severities being listed with duplicate timestamps.

This support was added in microsoft/vscode-languageserver-node#1630.

@jasonmalinowski jasonmalinowski requested review from a team as code owners May 12, 2025 21:53
@jasonmalinowski jasonmalinowski force-pushed the use-loggeroutputchannel branch from da1bf73 to e7eae1b Compare May 12, 2025 21:54
@jasonmalinowski jasonmalinowski self-assigned this May 13, 2025
10.0.0-next.15 brings full support for LogOutputChannels which cleans
up the logging of severities and timestamps. Otherwise we end up with
confusing duplicate severities being listed with duplicate timestamps.
Prior to moving things to LogOutputChannels, we implicitly controlled
the log level of the LSP traces by the log level of our main output
channel: as long as that was debug or trace, we'd also output the LSP
traces. Now each channel behaves independently, with the requirement
that if you want LSP tracing, you must set the trace channel to 'trace'
level. The other settings don't do anything.
@jasonmalinowski jasonmalinowski force-pushed the use-loggeroutputchannel branch from e3d98c0 to 6d28b76 Compare August 6, 2025 19:57
@jasonmalinowski jasonmalinowski merged commit 434a49d into dotnet:main Aug 6, 2025
32 checks passed
@jasonmalinowski jasonmalinowski deleted the use-loggeroutputchannel branch August 6, 2025 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants