Cannot generate a workspace snapshot

[shaal]

Bug description

After opening DrupalPod in Gitpod, I open the hamburger menu on top-left corner, and choose Gitpod: Share Workspace Snapshot

I see Capturing workspace snapshot dialog -

After a few minutes, it displays an error -

Errors in console:

(Using Gitpod's VScode v1.59)

Steps to reproduce

1. Open DrupalPod in gitpod:
   https://gitpod.io/#https://github.com/shaal/DrupalPod
2. Open the hamburger menu on top-left corner
3. Choose Gitpod: Share Workspace Snapshot

Expected behavior

I was able to take snapshots of DrupalPod workspace in the past, but somehow I can no longer able to.

Example repository

https://github.com/shaal/DrupalPod

Anything else?

I am able to create workspace snapshot on 'simpler' repos, such as - https://gitpod.io/#https://github.com/gitpod-io/template-typescript-node

[shaal]

I tested this also by opening https://github.com/gitpod-io/gitpod in Gitpod, and coose from the menu: Gitpod: Share Workspace Snapshot, same error.

[pawlean]

I could not replicate this. 🤔 This is what I see:

What version of VS Code are you on?

[shaal]

Vscode 1.59
I tried various browsers - Chrome, edge, Firefox. Still see the same error on both Gitpod repo and drupalpod repo.

[shaal]

I updated the description of this issue, to clarify this bug is happening only on some complex repos (DrupalPod, Gitpod, etc.), while on simpler repo (typescript demo workspace) I am able to create a snapshot.

[akosyakov]

I updated the description of this issue, to clarify this bug is happening only on some complex repos (DrupalPod, Gitpod, etc.), while on simpler repo (typescript demo workspace) I am able to create a snapshot.

GLB drops web socket connection each 10mins. Maybe it is bad luck that it happens in between.

[shaal]

@akosyakov I tested this multiple times, one after the other, different repos, etc.
Are you able to take a snapshot of Gitpod or drupalpod repos?

[akosyakov]

takeSnapshot server api hangs for very long time and eventually it gets dropped by GCP via closing the web socket in 10 mins. I think meta team should look why it is. cc @JanKoehnlein @gtsiolis

If it cannot be optimised then we should reconsider api, with notification from server instead of long running RPC call.

[gtsiolis]

I could reproduce the issue. Thanks @shaal for reporting and @akosyakov for the ping. 🏓

[csweichel]

/schedule