-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feat]: cull_idle_timeout mechanism requirement #5008
Comments
Please don't tag nhooyr - they are no longer working on the project. Thank you for the feature request! We're not adding new features at this time but we'll track it in the Backlog regardless. |
Thanks for reply, I am looking forward to this new feature. Could you please change the label to feature instead of enhancement? I think this is wrongly classified and it seems that I cannot change it myself. |
Whoever works on this consider how it might interop with |
I have searched these two params but I failed to find how to use them. Are they supported in the newest version 4.12.0? If so, could u plz provide an example to use these two params? Thx~ |
No, these are not supported in any version of code-server currently. That was just a note that we should look into those VS Code flags since we might be able to leverage them or at least be inspired by them.
|
What is your suggestion?
Maybe cull_idle_timeout mechanism should be provided. If there hasn't been an active connection to code-server in X minutes, we should exit with status 0. It has been mentioned in #1636 @nhooyr
Why do you want this feature?
I am working on develop online VSCode support by code-server. To enhance the resource utilization rate, I require cull-idle-timeout mechanism. If users do not use for a period of time, I hope the container killed. According to the doc, code-server provides the heartbeat mechanism. If I keep the WebPage on but do nothing, the time of heartbeat will be updated every minute. This is not what I want.
Others
I have seen that such feature is referred like issue #1636. However, I failed to launch with --idle-timeout args. I want to confirm if such function is supported right now? If not, is there any methods to support my requirement? I'll appreciate it if someone could help.
The text was updated successfully, but these errors were encountered: