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

ws created then stopped in ws-eu will open in ws-us when started again in VS Code Desktop #18531

Closed
digiltd opened this issue Aug 16, 2023 · 2 comments
Labels
meta: stale This issue/PR is stale and will be closed soon team: team-experience type: bug Something isn't working

Comments

@digiltd
Copy link

digiltd commented Aug 16, 2023

Bug description

Workspaces that have been created through the browser to be worked on using VS Code Desktop work fine on the correct server e.g. myproject-ws-eu123.gitpod.io.

When they are restarted from a stopped state using the Gitpod tab in VS Code Desktop the url changes to myproject-ws-us123.gitpod.io.

Steps to reproduce

Start a new EU based workspace from a repo.

Choose Open in VS Code on Desktop

Type gp url in terminal, note the url

Stop the workspace.

Start the workspace from within VS Code

Screenshot 2023-08-16 at 21 30 45@2x

Type gp url again note the url.

Workspace affected

No response

Expected behavior

The workspace should be in the same territory when you restart it

(I accept that ws-eu123 might become ws-eu124)

Example repository

No response

Anything else?

No response

@digiltd
Copy link
Author

digiltd commented Oct 25, 2023

This is still a problem for me, i have stopped using the VS Code Gitpod integrated feature (that little arrow that starts a workspace from within vscode) and only open from the dashboard in a browser because it uses the wrong territory/country than the one it was originally created in.

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the meta: stale This issue/PR is stale and will be closed soon label May 23, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: team-experience type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants