"Create new collaboration session" command unavailable

[dometto]

On a fresh installation of openvscode-server, after installing the Open Collaboration Tools extension, the "Create new collaboration session" command is unavailable:

However, it does show up in the list of commands for the extension (assuming the create command is oct.createRoom):

Does this command require admin privileges at install time, by any chance? Is the extension not compatible with openvscode-server?

[msujew]

Hey @dometto,

do you have a workspace open? The extension is only able to create a session in case you have workspace open, otherwise there is nothing to share. See also:

open-collaboration-tools/packages/open-collaboration-vscode/package.json

Line 152 in eef1745

"enablement": "workbenchState != empty && !oct.connection"

[dometto]

...d'oh! That's right! Thanks for the quick help! I'll close this, but if you happen to have any tips about how to address the following, I'd be super grateful:

I'm running into a next problem, which is that after creating a session and joining it with VSCodium (locally), an error is visible:

The tooltip says: "Unable to resolve workspace folder (crypto is not defined)".

Anyway, thanks for the brilliant work on this project!

[msujew]

@dometto I've just tried starting everything in VSCodium, but creating and joining the session seems to work as expected:

Are you on the latest version of the extension (v0.3.1)? Are you also on the latest version of VSCodium (1.100.23258)?

[dometto]

I'm on the latest version of both, yes. I also notice that when I create a session in VSCodium, and join the session from openvscode-server, the workspace is briefly opened in openvscode-server, but then the browser immediately redirects away from it. So it looks as if somehow the openvscode-server side is not able to establish a proper session?

I think it's not a VSCodium issue; the same happens when I open a new window in openvscode-server, and try to join a session (hosted in my first openvscode-server window).

I'm wondering if this could have something to do with the fact that openvscode-server is being run behind a reverse proxy.

If you have any immediate thoughts about what I could investigate, very welcome! If not, I'll debug more and open a separate issue.

[msujew]

Ah, I didn't quite notice that this was involving openvscode-server. We actually do have an issue on that #84. It's likely that some code I had specifically written for the web version (i.e. no server, only frontend, like https://vscode.dev) might be interfering with the extension behavior in the server version. It's rather annoying that VSCode desktop and the browser version behave slightly differently when it comes to loading workspaces. I hadn't had any time to reproduce this yet, but should be able to do so next week.