- Notifications
You must be signed in to change notification settings - Fork6k
Add optional idle timeout shutdown#7177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
13754f3
tocc3c22d
Comparegskifstad commentedMay 30, 2025
hi! our team would love this feature as well. I see there is a stray merge conflict causing linter errors, but otherwise, is there anything blocking this PR? |
Yeah happy to merge this in if the conflicts and below are addressed. I think the heart counting inactivity and directly exiting the process is more than it should be doing. Maybe we could refactor so the heart has an
Something like that. I think if we have the flag as One other thing, we should check the |
I did this for my needs but realized there is a closed issue (not implemented) that is requesting the same thing.
Through the idle-timeout arg or IDLE_TIMEOUT environment variable, after the specified number of minutes since the heartbeat was last refreshed is detected, the code-server process shuts down. When run as the single process of a docker container, this just stops the container.
Fixes#1636