Use $/logTrace for server trace logs in Zed and VS Code
#12564
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
|
dhruvmanila
approved these changes
Jul 30, 2024
|
I pushed both the changes and verified in VS Code: |
dhruvmanila
changed the title
$/logTrace for server trace logs in Zed and VS Code
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Summary
This pull request adds support for logging via
$/logTraceRPC messages. It also enables that code path for when a client is Zed editor (as there's no way for us to generically tell whether a client prefers$/logTraceover stderr.Related to: #12523
/cc @dhruvmanila
Test Plan
I've built Ruff from this branch and tested it manually with Zed.