VSCode fails to open workspace after connecting

[dometto]

After successfully joining an OCT room using OpenVSCode (server) VSCodium, I briefly see an opened workspace, but the workspace is quickly closed. OCT status is indicated as 'Connected', but there is now shared workspace.

In both VSCodium and OpenVSCode server, there is a exclamation mark next to the workspace name (see screenshot). In VSCodium, this says Unable to resolve workspace folder (ENOPRO: 'No filesystem provider found for resource oct:/Open%20Collaboration%20Workspace%29/test')

In OpenVSCode server, the page refreshes too quickly to read the error message in the exclamation marks, but I see this in the JS console log:

Uncaught (in promise) CodeExpectedError: ENOPRO: No file system provider found for resource 'oct:/Open%20Collaboration%20%28Workspace%29/test/.vscode'
    ixt https://myserver.com/user/dometto/openvscode/stable-7d842fb85a0275a4a8e4d7e040d2625abbf7f084/static/out/vs/code/browser/workbench/workbench.js:8
    j https://myserver.com/user/dometto/openvscode/stable-7d842fb85a0275a4a8e4d7e040d2625abbf7f084/static/out/vs/code/browser/workbench/workbench.js:3815
    exists https://myserver.com/user/dometto/openvscode/stable-7d842fb85a0275a4a8e4d7e040d2625abbf7f084/static/out/vs/code/browser/workbench/workbench.js:3815
    s https://myserver.com/user/dometto/openvscode/stable-7d842fb85a0275a4a8e4d7e040d2625abbf7f084/static/out/vs/code/browser/workbench/workbench.js:576
    v https://myserver.com/user/dometto/openvscode/stable-7d842fb85a0275a4a8e4d7e040d2625abbf7f084/static/out/vs/code/browser/workbench/workbench.js:576
workbench.js:8:153

This is with version 0.3.5 of the extension on both clients.

[msujew]

Just to make sure: This exclusively effects the web server versions of OpenVSCode/VSCodium right? I just tried it with the desktop versions of VSCode and VSCodium and both seem to work fine.

I would assume that an update on VSCode's end has broken this (again). It used to work a few months before. See #150 which fixed the issue with confirmations in #84.

[msujew]

I just checked GitHub codespaces as well, which also continues to work as expected. Unfortunately, I don't have time right now to check this in the other server distributions, so I'll take a look at this next week.

[dometto]

I'm seeing this with OpenVCode (server) and VSCodium (desktop app). I'm running an OCT server from source based on this repo's main branch. Could it be that there's some kind of version mismatch between server and the client extensions?

[msujew]

I'm running an OCT server from source based on this repo's main branch. Could it be that there's some kind of version mismatch between server and the client extensions?

That shouldn't be an issue. I've just tried that as well, just to make sure; It's working on my machine at least.

However, I can indeed confirm that the extension doesn't work correctly when joining from the OpenVSCode server app. It reloads twice, which disposes the workspace. I'll take a look at that.

[msujew]

I've figured out what's wrong with our extension. It seems like some VSCode distributions (especially VSCode server) don't like loading workspace files. I'll provide a fix for this later this week, it requires a non-trivial change.