Skip to content
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

[server] Fix subscription-based default timeouts #4760

Closed
svenefftinge opened this issue Jul 9, 2021 · 3 comments · Fixed by #4819
Closed

[server] Fix subscription-based default timeouts #4760

svenefftinge opened this issue Jul 9, 2021 · 3 comments · Fixed by #4819
Assignees
Labels
component: server type: bug Something isn't working

Comments

@svenefftinge
Copy link
Member

svenefftinge commented Jul 9, 2021

Just surprisingly stumbled over the parallel workspace limit to learn that there were a couple of workspaces running for more than 45 minutes. I'm pretty sure I haven't accessed at least one of them.

Can someone please verify that started workspace where the browser tab idles in the background, actually to time out?

@svenefftinge
Copy link
Member Author

Update: after an hour (I'm on the professional open-source plan) one of the workspaces timed out.
So maybe it is just that the prof open-source account has 1h timeouts (unlike shown in the UI)?

@csweichel
Copy link
Contributor

Turns out the default timeouts broke during the migration away from gitpod-com:

right now, every user gets a default timeout of 1h.

@csweichel csweichel changed the title Do timeouts on idling workspaces really work? [server] Fix subscription-based default timeouts Jul 12, 2021
@csweichel csweichel added component: server type: bug Something isn't working labels Jul 12, 2021
@csweichel
Copy link
Contributor

When fixing this, we must do this in a way that doesn't break self-hosted

@geropl geropl self-assigned this Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: server type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants