-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Move the "close timeout" (IDE + editor timeout) to a user preference. #16089
Comments
We will revisit on 20 Feb 2023. |
This is marked complete (I think by accident) but the UI is not yet implemented, re-opening. |
Closing this as it has been resolved in #16503. Cc @iQQBot @loujaybee |
@gtsiolis ah, there might be some confusion. This issue is related to the editor timeout, not the inactivity timeout (#9038). Updates to editor timeouts were descoped from the other PR to get the change merged, and follow up with additional changes for the editor timeout. Will re-open. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Currently, when an editor disconnects from Gitpod, the workspace timeout is then "reset" to 5 minutes. This means that when a user uses the newly implemented
gp timeout set
command that closing the editor will still close the workspace after 5 minutes. The user should be able to control this editor timeout value, and when extending the workspace timeout should be able to ensure that the workspace will not close, despite the editor closing.See related comment
See internal conversation.
Related to:
The text was updated successfully, but these errors were encountered: