You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
馃悰 Describe the bug
When changing VS Code settings from UI or directly in settings.json (from within VS Code) auto-upload is not triggered as it used to. Now, manual upload is necessary to update the Gist.
馃尨 Visual Studio Code Version : 1.53.0 (user setup)
馃尨 Code Settings Sync Version : v3.4.3
馃尨 Standard or Insiders : Standard
馃尨 Portable or Installed : Installed
馃尨 OSS or Official Build : Official Build
馃尨 Operating System : Windows_NT x64 10.0.19041
馃尨 Occurs On: Upload
馃尨 Proxy Enabled: No
馃摪 To Reproduce
Steps to reproduce the behavior:
Open VS Code preferences UI or settings.json (through command palette)
Change a / some setting/s
Save
Notice no upload message in status bar
No new revision to Gist either
馃挭 Expected behavior
Expecting change in settings, regardles of through UI or settings.json, to trigger auto-upload as it used to do.
馃摵 Console Error Log
No errors to be found. I will be happy to provide further info and to do some testing, if necessary.
The text was updated successfully, but these errors were encountered:
馃悰 Describe the bug
When changing VS Code settings from UI or directly in settings.json (from within VS Code) auto-upload is not triggered as it used to. Now, manual upload is necessary to update the Gist.
馃尨 Visual Studio Code Version : 1.53.0 (user setup)
馃尨 Code Settings Sync Version : v3.4.3
馃尨 Standard or Insiders : Standard
馃尨 Portable or Installed : Installed
馃尨 OSS or Official Build : Official Build
馃尨 Operating System : Windows_NT x64 10.0.19041
馃尨 Occurs On: Upload
馃尨 Proxy Enabled: No
馃摪 To Reproduce
Steps to reproduce the behavior:
馃挭 Expected behavior
Expecting change in settings, regardles of through UI or settings.json, to trigger auto-upload as it used to do.
馃摵 Console Error Log
No errors to be found. I will be happy to provide further info and to do some testing, if necessary.
The text was updated successfully, but these errors were encountered: