The workspace stops due to idle timeout setting while the workspace is in use.
See original GitHub issueDescribe the bug
I set the workspace idle timeout to 1 minute to test the workspace idle timeout and create a workspace with the code-server editor. At that time, the workspace stops even though I am using the terminal and editor. If I set the workspace idle timeout, is it normal to stop the workspace while in use? If this is an abnormal operation, I wonder what setting is necessary for normal operation.
Che version
- latest
- nightly
- other: 7.4.0
Steps to reproduce
Expected behavior
Runtime
- kubernetes (include output of
kubectl version
) - Openshift (include output of
oc version
) - minikube (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Screenshots
Installation method
- chectl
- che-operator
- minishift-addon
- helm
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- other: please specify
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Manage the WorkSpace running mode - AWS Documentation
To set the automatic stop time, select the WorkSpace in the Amazon WorkSpaces console, choose Actions, Modify Running Mode Properties, and then set...
Read more >EPM Workspace Timeouts
EPM Workspace closes the session when the user has stopped using EPM Workspace but has not closed the browser. If there is no...
Read more >How to Configure Idle and Disconnect Timeout Settings in ...
Click the Start menu, select All Programs Citrix > Administrative Tools > Citrix > Administration Tools > ICA Listener Configuration. Select the ICA-TCP ......
Read more >The Workspace ONE UEM server or platform must be ...
Details · 1. Authenticate to the Workspace ONE UEM console as the administrator. · 2. Navigate to Groups & Settings >> All Settings...
Read more >All About APEX Timeouts
Instance Timeout Settings; Workspace Timeout Settings ... I am using the Maximum Session Length in Seconds setting, but it works the same ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sleshchenko Thank you for your help. Tested on the latest version, the timeout does not work the same as the previous version.
@kellyhyomin At the center there should be proposal to restart workspace in debug mode, if no - there is context menu that allows you to start in debug mode. See https://www.eclipse.org/che/docs/che-7/troubleshooting-for-che-end-users/#restarting-a-che-workspace-in-debug-mode-after-start-failure_troubleshooting-for-che-end-users
Maybe it’ll show the real reason. I assume typescript needs theia to start… So, please disable all plugins that fail to start, test workspace idling - if it works - close this issue. If you need a help with code-server and theia plugin - please open a new issue. Thanks.