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

Extensions settings cleared in uploaded gist; subsequent download flushes all installed extensions #789

Closed
tillig opened this issue Mar 6, 2019 · 6 comments
Labels

Comments

@tillig
Copy link

tillig commented Mar 6, 2019

🐛 Describe the bug
As of version 3.2.6, any time I upload my settings to my gist, the list of extensions in extensions.json is entirely empty. Thus, if I then download my settings in a different instance of VS Code... it removes all extensions.

🌴 Visual Studio Code Version : 1.31.1
🌴 Code Settings Sync Version : 3.2.6
🌴 Standard or Insiders : Standard
🌴 OSS or Portable : OSS
🌴 Operating System : Windows 10
🌴 Occurs On: Upload
🌴 Proxy Enabled: No
🌴 Gist Id: It appears the syncSettings.json file contains a token of some nature; I'd prefer to not pass that around.

📰 To Reproduce
Steps to reproduce the behavior:

  1. Ctrl+Shift+P, Upload Settings
  2. View gist for extensions.json - it's empty ([])

💪 Expected behavior
The extensions should be in there.

@chalkygames123
Copy link

Related: #756

@tillig
Copy link
Author

tillig commented Mar 6, 2019

Yep, could be duplicate. I am using the installed version of VS Code, not portable, but it sounds the same.

@shanalikhan
Copy link
Owner

Yes, it will be fixed a day or two.

@LuisUrrutia
Copy link
Contributor

So sorry, my PR #782 broke the extension sync on windows systems because the path delimiter (Linux/macOS: / and Windows \) but it should be fixed with #791.
@shanalikhan I think that It should be released as a hotfix, right?

@shanalikhan
Copy link
Owner

shanalikhan commented Mar 6, 2019

released v3.2.7
let me know if there is any error.

@tillig
Copy link
Author

tillig commented Mar 6, 2019

Just tried it, works great. Thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants