Skip to content

Can't open workspace in VS code #8092

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

Closed
rogwild opened this issue Feb 8, 2022 · 11 comments
Closed

Can't open workspace in VS code #8092

rogwild opened this issue Feb 8, 2022 · 11 comments
Assignees

Comments

@rogwild
Copy link

rogwild commented Feb 8, 2022

Bug description

Can't open workspace in VS code, it works only in browser.
VS code opens, but I have this error in console

[2/8/2022, 4:48:02 PM] open workspace window: vscode://gitpod.gitpod-desktop/workspace/dashboard-backend?%7B%22instanceId%22%3A%223a19cba6-988b-4e56-b181-5673de35a608%22%2C%22workspaceId%22%3A%22zenfuse-dashboardbacken-qxv2g3wahv1%22%2C%22gitpodHost%22%3A%22https%3A%2F%2Fgitpod.io%22%7D
[2/8/2022, 4:48:03 PM] acquiring lock: gitpod.io
[2/8/2022, 4:48:03 PM] acquired lock: gitpod.io
[2/8/2022, 4:48:03 PM] fetching the local app from https://gitpod.io/static/bin/gitpod-local-companion-darwin
[2/8/2022, 4:48:03 PM] released lock: gitpod.io
[2/8/2022, 4:48:03 PM] the local app (pid: 1266) is running, but the api endpoint is not ready: Error: Response closed without headers
[2/8/2022, 4:48:03 PM] retying again after 1s delay...
[2/8/2022, 4:48:04 PM] the local app (pid: 1266) is running, but the api endpoint is not ready: Error: Response closed without headers
[2/8/2022, 4:48:04 PM] retying again after 1s delay...

Снимок экрана 2022-02-08 в 16 49 40

Steps to reproduce

  1. Open workspace
  2. Click button "Gitpod: Open in VS code" in left top menu
  3. Open output logs of Gitpod extension in VS code

Workspace affected

zenfuse-dashboardbacken-qxv2g3wahv1

Expected behavior

No response

Example repository

No response

Anything else?

No response

@akosyakov
Copy link
Member

Try to close VS Code and kill all processes with gitpod in name and then try again. Also you should see show logs after sometime in bubble notification. Is there anything suspicious there?

@rogwild
Copy link
Author

rogwild commented Feb 8, 2022

What console command should I run on MacOS?

@mikenikles
Copy link
Contributor

mikenikles commented Feb 12, 2022

I don't even see the "Gitpod" extension in the output dropdown. When I click "Gitpod: Open in VS Code Insiders" in my running workspace, the local VS Code Insiders starts, asks me if I want to allow an extension to open a URI and when I accept that, nothing happens.

local-vs-code-does-not-open-workspace.mp4.mp4

@shaal
Copy link
Contributor

shaal commented Feb 12, 2022

I see what @mikenikles screen recording show.
When I try again, I get a little further, where it make an initial connection with the local vscode, and I choose continue, but then getting an error that connection cannot be established.
image

[2/11/2022, 10:22:55 PM] open workspace window: vscode-insiders://gitpod.gitpod-desktop/workspace/DrupalPod?%7B%22instanceId%22%3A%221653762d-5c33-4c56-ba49-59e8a71df273%22%2C%22workspaceId%22%3A%22shaal-drupalpod-ywpnb871psp%22%2C%22gitpodHost%22%3A%22https%3A%2F%2Fgitpod.io%22%7D
[2/11/2022, 10:22:55 PM] acquiring lock: gitpod.io
[2/11/2022, 10:22:55 PM] acquired lock: gitpod.io
[2/11/2022, 10:22:55 PM] fetching the local app from https://gitpod.io/static/bin/gitpod-local-companion-darwin
[2/11/2022, 10:22:56 PM] released lock: gitpod.io

@shaal
Copy link
Contributor

shaal commented Feb 12, 2022

I tried this also with local regular VSCode (not the insiders version) - it worked!
The failure I had in the previous comment, is with insiders version of VS Code.

@loujaybee loujaybee moved this to Scheduled in 🚀 IDE Team Feb 14, 2022
@loujaybee
Copy link
Member

loujaybee commented Feb 14, 2022

Moving to scheduled as it looks related to the current insiders version, let's investigate.

Thanks @rogwild, @shaal, @mikenikles ! 🙏

@loujaybee loujaybee self-assigned this Apr 6, 2022
@MHipo
Copy link

MHipo commented May 1, 2022

Tried opening gitpod remote on VSCODE desktop and got this error log:

[Info  - 12:25:10.281] released lock: gitpod.io
[Error  - 12:25:10.351] failed to access the local app: Error: workspace not found
[Error  - 12:25:10.351] failed to open uri: Error: workspace not found 

The corresponding log file says:

time="2022-05-01T14:19:00+02:00" level=error msg="cannot get workspace" WorkspaceID=workspace_name error="jsonrpc2: code 403 message: operation not permitted: missing get permission on workspace"
time="2022-05-01T14:20:49+02:00" level=error msg="cannot get workspace" WorkspaceID=workspace_name error="jsonrpc2: code 403 message: operation not permitted: missing get permission on workspace"
time="2022-05-01T14:25:10+02:00" level=error msg="cannot get workspace" WorkspaceID=workspace_name error="jsonrpc2: code 403 message: operation not permitted: missing get permission on workspace"

@CNSKnight
Copy link

Experiencing this now as @MHipo described.
Fresh githubrepo/gitpod project/workspace.
Thinking may be a lag in cloud readiness for local vscode loading?

@MHipo
Copy link

MHipo commented May 17, 2022

@CNSKnight I also noticed collaborating is also difficult (as the Gitpod plugin might throw the similar error), because it is impossible to open a particular workspace - locally on the Vscode desktop. Did you try opening a workspace as a collaborator of a repo?

@defactojob
Copy link

i am getting the same error message using regular VSCode (non-insider)

@loujaybee
Copy link
Member

The above issue / logs mention local companion, which will be considered legacy for VS Code Desktop very soon:
https://www.gitpod.io/docs/ides-and-editors/vscode#connect-to-vs-code-desktop-using-local-companion-legacy

Please can you try following the steps mentioned in this blog post:
https://www.gitpod.io/blog/vscode-desktop-ssh-updates

To use the SSH Gateway approach of connecting to VS Code Desktop.

Ensure your user settings in VS Code have gitpod.remote.useLocalApp set to false, which should force usage of the new connection method. You'll either need to copy the access token into the password prompt, or setup an SSH key (suggested).

I'm going to close the issue, please try the above steps, if you're still having issues, please let us know 🙏

@loujaybee loujaybee closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2022
@akosyakov akosyakov moved this from Scheduled to Done in 🚀 IDE Team Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

9 participants