Repository navigation
Keep the output channel of the language server across restarts - #29
Merged
Merged
Conversation
The language client closes an output channel that it created itself when it stops. If the language server logs anything after that, writing to the closed channel throws an uncaught error in the extension host. Use a single channel for the lifetime of the extension instead. This also keeps the logs of the previous language server when it restarts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #29 +/- ##
==========================================
+ Coverage 93.67% 93.71% +0.03%
==========================================
Files 21 21
Lines 2325 2339 +14
Branches 350 350
==========================================
+ Hits 2178 2192 +14
Misses 110 110
Partials 37 37
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or 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
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.
The language client closes an output channel that it created itself when it stops. The language server can still log after that, for example a warning from a slow ESGF query or from pygls about a request that arrived during shutdown. Writing that line to the closed channel throws an uncaught
Channel has been closederror in the extension host.This made the
VSCode stablejob fail intermittently, on whichever test was running at the time, as in #22.The extension now creates one output channel for its whole lifetime and passes it to each client, so the client does not close it. This also keeps the logs of the previous language server after a restart, instead of replacing the channel.
Testing
I added a test that fails with this error without the fix. It writes to the channel after a restart. To do that, the extension's test API now exposes
outputChannel.Repeated runs of the VSCode tests with VSCode stable, on Xvfb:
main, without the fixmainwith the fix🤖 Generated with Claude Code