Server Explorer Not Showing After Disconnect and Workspace Reopen

[hsyhhssyy]

When I'm working, I typically uncheck "Servers" and check "Explorer" in the Server Manager, as shown below:

However, I’ve noticed that if VSCode is closed while connected to an environment (as in the setup above), and then reopened when that server is no longer available, the Server Manager appears blank, like this:

In this case, it seems necessary to re-check "Servers" in order to display the Server Explorer again. Otherwise, it’s not possible to initiate a connection, as the status bar link also doesn't appear.

This behavior seems to have changed after version 3.0.0. In earlier versions, such as before 3.0.0, the "Explorer" would still be displayed and a progress indicator would appear while attempting to reconnect. I believe this might be a bug.

[isc-bsaviano]

Hi @hsyhhssyy, what do you mean by "when that server is no longer available"? Do you mean you shut the server down in between closing VS Code and then re-opening that local folder?

[hsyhhssyy]

Hi @hsyhhssyy, what do you mean by "when that server is no longer available"? Do you mean you shut the server down in between closing VS Code and then re-opening that local folder?

Yes, I mean that the remote server becomes unreachable after closed and before reopening the workspace. It's reachable when closing, but not after reopening, such as VPN disconnected.

[isc-bsaviano]

Thanks for clarifying @hsyhhssyy. Can you turn on the objectscript.outputRESTTraffic setting before you close VS Code, restart it with the server inaccessible, and then send me the contents of the ObjectScript Output channel? That might help diagnose what's going wrong.

[isc-bsaviano]

I think I know the cause. VS Code attempts to open every configured server connection in the workspace upon extension activation. This will delay activation until all of the requests resolve. #1440 added code that would terminate these requests if they took too long, but it initially didn't work due to an VS Code issue (microsoft/vscode#227805). I believed that the VS Code issue was fixed at some point, but it must not have been fully resolved. I will see if there's an alternate way to implement this that doesn't rely on the VS Code team fixing the underlying issue.

[isc-bsaviano]

@hsyhhssyy Turns out this was always a bug in our extension and not VS Code. I have opened a PR with a proposed fix. You can try it out using the VSIX in the zip attached below.

vscode-objectscript-3.0.3-dev.1577.vsix.zip