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

Codespaces - Setting Sync does not work after addition of prompt syncing #241355

Open
glektarssza opened this issue Feb 20, 2025 · 0 comments
Open
Assignees

Comments

@glektarssza
Copy link

glektarssza commented Feb 20, 2025

Seems to have been triggered by the merge of #241123. Setting sync was working fine yesterday.

Does this issue occur when all extensions are disabled?: Yes

VSCode Version:

Version: 1.98.0-insider
Commit: f23861839fb21c44102dac215998647b4cd02840
Date: 2025-02-20T05:04:30.237Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36

OS Version:

uname -a
> Linux codespaces-5883da 6.5.0-1025-azure #26~22.04.1-Ubuntu SMP Thu Jul 11 22:33:04 UTC 2024 x86_64 GNU/Linux
source /etc/os-release
echo $PRETTY_NAME
> Debian GNU/Linux 12 (bookworm)

Steps to Reproduce:

  1. Open a GitHub Codespace
  2. Sync settings
  3. Observe everything breaks down

Video of bug occurring:

broken_codespace.mp4

Additional notes:

  • There is a proxy between me and vscode-sync-insiders.trafficmanager.net that may be resulting in the HTTP 403 observed in the setting sync logs. Not sure and unclear how to test if this is the case.
  • Turning of the syncing of prompts restores setting sync functionality.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants