Attempt to install extensions in workbench that fail to install from remote code-server

[joshspicer]

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 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 server

The workbench can reach the marketplace and is able to perform the installation.

b73d660:
https://github.com/user-attachments/assets/e39e04f1-2ac7-426c-b0e1-53f0905e9ba5

[sandy081]

@joshspicer Thanks for the initiation. Instead of adding a new failed property, I would use the existing whenExtensionsReady method. Please change it to return all extension IDs or URIs that server should be initialised with. Eg:

whenExtensionsReady(): Promise<Array<string|URI>>

On the workbench, add a new contribution similar to

vscode/src/vs/workbench/contrib/extensions/electron-sandbox/remoteExtensionsInit.ts

Line 28 in f0c1f4d

export class RemoteExtensionsInitializerContribution implements IWorkbenchContribution {

that installs extensions which are missing on the remote.

[joshspicer]

Demo

demo2.mov

Notes

• Remote - SSH directly connects to the code-server instance hardcoded on port 25565
• The code-server process cannot reach marketplace.visualstudio.com. (Blocked for only that program via firewall utility)

• I've simulated a "failed" VSIX installation on the server-side by appending .BROKEN to the file name on startup and re-naming before the workbench connects.
  • This is a bit contrived, but I wanted to show that this functionality indeed works

[vs-code-engineering]

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

[sandy081]

Please check the comments

[sandy081]

Since, I will be not available from tomorrow, I would like to unblock you by giving the approval assuming that you will take care of the review feedback.

Thanks

[joshspicer]

changes from last review: 5a401fa