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

Fix default vscode settings sync value #9278

Merged
merged 1 commit into from
Apr 19, 2022
Merged

Fix default vscode settings sync value #9278

merged 1 commit into from
Apr 19, 2022

Conversation

jeanp413
Copy link
Member

@jeanp413 jeanp413 commented Apr 13, 2022

Description

Fix default vscode settings sync value

How to test

  1. Bundle gitpod-desktop vsix from Implement gitpod auth and settings sync openvscode-server#337 Dowload this vsix file gitpod-desktop-0.0.30.zip
  2. Install vsix in vscode desktop
  3. Press F1 and execute Gitpod: Turn on Settings Sync command
  4. Close all windows
  5. Reopen vscode and enable settings sync: Press f1 and execute Settings Sync: Turn On... command (make sure you have some local settings already modified)
  6. When it prompts to resolve conflicts, choose manual
  7. Observe diff editor for settings.json shows remote value as {} (empty object) instead of {settings:""}

Release Notes

NONE

@jeanp413 jeanp413 requested a review from a team April 13, 2022 02:51
@jeanp413 jeanp413 requested a review from akosyakov April 13, 2022 02:51
@github-actions github-actions bot added the team: webapp Issue belongs to the WebApp team label Apr 13, 2022
@akosyakov
Copy link
Member

@jeanp413 It would be nice if you can provide vsix file, otherwise it takes time to verify.

@jeanp413
Copy link
Member Author

jeanp413 commented Apr 13, 2022

Added the vsix file in description

@geropl
Copy link
Member

geropl commented Apr 13, 2022

I'm not sure how to test this. I followed the steps, but I did not see a conflict (used to sync with GitHub...?).
I assume I skipped some prior steps to do?

@geropl geropl self-assigned this Apr 13, 2022
@jeanp413
Copy link
Member Author

@geropl sorry about that I missed some steps, I updated it in the description.

@akosyakov
Copy link
Member

Setting sync worked for me, but I did not see any resolve conflict windows and could not follow verification steps because of it.

@akosyakov
Copy link
Member

Settings sync worked btw, but extensions although synced were not installed, also I see errors in setting sync output:
Screenshot 2022-04-14 at 09 39 51
Screenshot 2022-04-14 at 09 40 02

Here exported logs: vscodeLogs.zip

btw we should generate better file names for logs, something like ${workspace-id}-vscode-web-logs.zip

@jeanp413
Copy link
Member Author

jeanp413 commented Apr 14, 2022

@akosyakov I see you had already some data in your account try deleting your sync data first and then settings sync again in vscode desktop
About the error seems an issue with openvsx maybe you were just unlucky, could you try again

[2022-04-14 09:37:01.468] [window] [error] [Extension Host] Fetch failed while querying open-vsx FetchError: network timeout at: https://open-vsx.jp-oauth-test.staging.gitpod-dev.com/api/-/query
	at Timeout.<anonymous> (/ide/extensions/gitpod-web/dist/extension.js:2:666420)

btw we should generate better file names for logs, something like ${workspace-id}-vscode-web-logs.zip

we don't have acces to workspace-id in core vscode unless we parse the gitpod extension logs file before zipping it

@geropl
Copy link
Member

geropl commented Apr 19, 2022

I tested again, and see:

  • {} for settings.json
  • empty file for keybindings.json
  • [] for extensions.json
    @jeanp413 Is that expected?
    image

@jeanp413
Copy link
Member Author

jeanp413 commented Apr 19, 2022

@geropl yep that's fine, that's from the theia settings migration logic fine for now until we remove it 👍

@roboquat roboquat merged commit 078a43f into main Apr 19, 2022
@roboquat roboquat deleted the jp/oauth-test branch April 19, 2022 14:19
@roboquat roboquat added deployed: webapp Meta team change is running in production deployed Change is completely running in production labels Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: webapp Meta team change is running in production deployed Change is completely running in production release-note-none size/XS team: webapp Issue belongs to the WebApp team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants