question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow admins to change workspaces inactivity and run timeout

See original GitHub issue

Is your enhancement related to a problem? Please describe

Before switching to the DevWorkspace engine, it was possible to specify workspaces timeout through Che server properties CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT and CHE_LIMITS_WORKSPACE_RUN_TIMEOUT.

Currently Che-Theia based workspaces are idled after 15 minutes of inactivity. This is specified in the editor definition and it’s not configurable by the user or by an admin (if not by patching the editor definition in the plugin registry or by publishing and using an alternative editor definition).

Note that VS Code and JetBrains IDE based workspaces are never idled and that we want to use a universal idling mechanism (there is a separate issue for that).

Describe the solution you’d like

CheCluster CRD should have:

  • devEnvironments.secondsOfInactivityBeforeIdling
  • devEnvironments.secondsOfRunBeforeIdling

That should be propagated as environment variables to the workspace containers:

  • SECONDS_OF_DW_INACTIVITY_BEFORE_IDLING
  • SECONDS_OF_DW_RUN_BEFORE_IDLING

Machine exec should parse those variables, if they exist, when setting the timeout.

Machine exec should support SECONDS_OF_DW_RUN_BEFORE_IDLING

Theia definition should not specify the --idle-timeout parameter for machine exec.

The defaults should be 30 minutes for secondsOfInactivityBeforeIdling and SECONDS_OF_DW_INACTIVITY_BEFORE_IDLING and -1 for secondsOfRunBeforeIdling and SECONDS_OF_DW_RUN_BEFORE_IDLING

Additional context

https://github.com/eclipse/che/issues/21322

Release notes text

Administrators can specify the timeout for inactivity and running workspaces with the CheCluster spec.devEnvironmentfieldssecondsOfInactivityBeforeIdlingandsecondsOfRunBeforeIdling` respectively. The default values are 30 minutes and -1 (no timeout) respectively.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:16 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
dkwon17commented, Jul 21, 2022

@l0rd , yes this can be closed and included in the 7.51 release notes

1reaction
pdfruthcommented, Jun 30, 2022

Thank You @l0rd. I can confirm that the addition of a devfile has enabled the che-code editor to load. And there is no idle timeout!!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Manage your Windows WorkSpaces - AWS Documentation
To allow the user to override your settings, choose Overridable Administrator Settings; otherwise, choose Not Overridable Administrator Settings.
Read more >
Idle session timeout for Microsoft 365 - Microsoft 365 admin
In the Microsoft 365 admin center, select Org Settings -> Security & privacy tab and select Idle session timeout. On the Idle Session...
Read more >
Configuring RDP/RDS Sessions Limits (Timeouts) on Windows
Set time limit for active but idle Remote Desktop Services sessions — the policy allows to end idle RDP sessions that have no...
Read more >
2.4 Configuring Workspace Preferences - Oracle Help Center
Enter a positive integer to control the default idle time for sessions used by applications in this workspace. · Enter 0 to switch...
Read more >
Control session timeout in Google Workspace - Goldy Arora
As now we have understanding of what session is, and we also know about Google Workspace's default session, let us configure it.​ ·...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found