Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode Server Setting Sync does not sync remote extensions #182364

Closed
SuhasHebbar opened this issue May 13, 2023 · 1 comment
Closed

VSCode Server Setting Sync does not sync remote extensions #182364

SuhasHebbar opened this issue May 13, 2023 · 1 comment
Assignees

Comments

@SuhasHebbar
Copy link

SuhasHebbar commented May 13, 2023

Does this issue occur when all extensions are disabled?:
Extensions are necessary to trigger this issue

  • VS Code Version: 1.78.2
  • OS Version: linux

Steps to Reproduce:

  1. Setup vscode server on two different machines A & B (both linux in my case)
  2. Install browser and remote extensions on machine A using vscode.dev remote tunnel.
  3. Open vscode server using vscode.dev remote tunnel on machine B.
  4. Browser extensions and settings.json are synced, but remote extensions are not synced. In this case since machine B is a fresh instance no extensions were installed prior to enabling setting sync.

I can only sync the remote extensions from A to B by manually exporting the settings to a file on A and them importing the settings file on machine B.

@SuhasHebbar
Copy link
Author

SuhasHebbar commented May 13, 2023

Just found that this is marked as Won't fix by Microsoft in #90968.

Unfortunate, but back to Neovim it is I suppose.

EDIT: Okay it does kinda work. A bit finicky. What was happening was that the vscode-server on machine B was wiping
the changes to extensions.json made by machine A. You can manually force machine A's extension.json in the Settings Sync view and get the extensions installed, but not as reliable as one would like it.

Sorry for cluttering the issue tracker for y'all.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants