Skip to content

Use LogOutputChannel - #1630

Merged
Dirk Bäumer (dbaeumer) merged 4 commits into
mainfrom
dbaeumer/eastern-flea-coffee
May 12, 2025
Merged

Dirk Bäumer (dbaeumer) merged 4 commits into
mainfrom
dbaeumer/eastern-flea-coffee

Conversation

@dbaeumer

Copy link
Copy Markdown
Member

No description provided.

@dbaeumer
Dirk Bäumer (dbaeumer) marked this pull request as ready for review May 12, 2025 10:21
@dbaeumer
Dirk Bäumer (dbaeumer) enabled auto-merge (squash) May 12, 2025 10:21
@vs-code-engineering vs-code-engineering Bot added this to the May 2025 milestone May 12, 2025
@dbaeumer
Dirk Bäumer (dbaeumer) merged commit c4e2864 into main May 12, 2025
@dbaeumer
Dirk Bäumer (dbaeumer) deleted the dbaeumer/eastern-flea-coffee branch May 12, 2025 10:29
Davy Landman (DavyLandman) pushed a commit to usethesource/rascal-language-servers that referenced this pull request Jul 2, 2026
The update of `vscode-languageclient` to `10.x` in #1114 changed logging
behaviour, since the logger is now a `LogOutputChannel` by default
(instead of an `OutputChannel` -
microsoft/vscode-languageserver-node#1630).

Where before, we received `OuptuChannel::append` calls for LOG4J
messages from the language server, this has changed to
`LogOutputChannel::error` calls, enabled by the more refined logger type
in the client. This is probably because LOG4J uses the standard error
stream.
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