[draft] Attempt to install extensions in workbench that fail to install from remote code-server #238815
+94
−19
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.
related: microsoft/vscode-remote-release#9994 , microsoft/vscode-remote-release#5927 (comment) , microsoft/vscode-remote-release#9090 , microsoft/vscode-remote-release#9454 (comment)
Provides a way for the remote server to report back extensions that it could not install. The workbench can read this value and attempt to install these of extensions.
This is useful in cases when a remote does not have access to the marketplace, but a local machine does. This will effectively proxy the installation of an extension through the user's machine, closing several Remote - SSH issues
See early demo below showing the end-to-end. This demo uses a modded Remote - SSH that will connect to a server pre-started on my local machine. That server process is blocked from accessing
marketplace.visualstudio.com
, causing an error to be thrown in the serverThe workbench can reach the marketplace and is able to perform the installation.
b73d660:
Screen.Recording.2025-01-26.at.7.11.48.PM.mov