feat: Handle disconnection according to the dev workspace status

[RomanNikitenko]

Signed-off-by: Roman Nikitenko [email protected]

What does this PR do?

Handle disconnection according to the dev workspace status:

• Run timeout

• Inactivity timeout

• An error

• Workspace is not running

Within testing I detected the following unusual use case:

• the disconnection happened
• the API responds that the workspace is running
• dashboard displays the workspace as running
• but the workspace is not usable

I've added some logic to propose reloading the window for such use case - it fixes the disconnection. See the behaviour on the video.

reload_window.mp4

What issues does this PR fix?

eclipse-che/che#21610

How to test this PR?

It's possible to change the corresponding properties to test use cases related to timeouts:

See screenshot here

Run timeout

1. Set the workspace run timeout (checluster.spec.devEnvironments.secondsOfRunBeforeIdling) to 120, for example.
2. Wait about 120 seconds.
3. The corresponding dialog should be displayed.

Inactivity timeout

1. Set the workspace inactivity timeout (checluster.spec.devEnvironments.secondsOfInactivityBeforeIdling) to 100, for example.
2. Do not interact with the workspace 100 seconds.
3. The corresponding dialog should be displayed.

An error

I tested the use case using minikube:

• start a workspace using minikube
• go to your local terminal => minikube ssh => docker ps
• detect a container with the running VS Code and stop it, like: docker stop d9bd0222b513

Workspace is not running

The use case is related to the any case when

• a workspace is not running
• we can not detect an error, timeout or any reason of the stopped workspace

You can just stop a workspace using dashboard to test it.

[github-actions]

Click here to review and test in web IDE:

[github-actions]

Click here to review and test in web IDE:

[azatsarynnyy]

To test the situation when the user might receive this message

I've just sent a SIGKILL to the VS Code process from its terminal (kill -9 pid). In this case, DevWorkspace is still running, but VS Code is not.

[azatsarynnyy]

I tested different use cases - everything works as described 👍

Thanks for updating the rebase rules.

[devstudio-release]

Build 3.5 :: code_3.x/290: Console, Changes, Git Data

[devstudio-release]

Build 3.5 :: sync-to-downstream_3.x/2025: Console, Changes, Git Data