Prefer workspace extension host #151
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
colin-grant-work
approved these changes
Nov 7, 2024
thegecko
force-pushed
the
remote-support
branch
from
45443af to
ea344aa
Compare
👍 Added a changelog entry |
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.
What it does
This changes the exensionKind so that the extension prefers to run in the workspace. This enables remote VS Code sessions (e.g. WSL, ssh-remote, codespaces) to execute the memory inspector in the workspace where the debugger is more likely to be. Fixes #150
How to test
Run a debugger in WSL and use this extension
Review checklist
Reminder for reviewers