You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is confused which one should be configured. Actually, CHE_WORKSPACE_AGENT_DEV_INACTIVE__STOP__TIMEOUT__MS is deprecated and should be removed at all. Maybe we should add the corresponding alias. Then CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT will be used as the only one property for configuration idle timeout:
for all workspaces in case of single user Che;
default the idle timeout per user which can be overridden with Resources API.
Reproduction Steps
Login as admin.
Set the idle timeout to 24h for User A.
Login as User A.
Start workspace and close browser tab.
Reopen workspace after 2h.
Expected: Workspace is active because the idle timeout is overridden for the particular user.
Actual: Workspace is stopped after 1h because it is default timeout that is configured with che.workspace.agent.dev.inactive_stop_timeout_ms.
The text was updated successfully, but these errors were encountered:
Description
Unable to override idle timeout for a particular user.
It happens because of lack special implementation of
WorspaceActivityManager
in multiuser Che, like Codenvy has HostedWorkspaceActivityManager.Also there are two properties for configuring the ilde timeout:
It is confused which one should be configured. Actually,
CHE_WORKSPACE_AGENT_DEV_INACTIVE__STOP__TIMEOUT__MS
is deprecated and should be removed at all. Maybe we should add the corresponding alias. ThenCHE_LIMITS_WORKSPACE_IDLE_TIMEOUT
will be used as the only one property for configuration idle timeout:Reproduction Steps
Expected: Workspace is active because the idle timeout is overridden for the particular user.
Actual: Workspace is stopped after 1h because it is default timeout that is configured with
che.workspace.agent.dev.inactive_stop_timeout_ms
.The text was updated successfully, but these errors were encountered: