Shared workspace times out if workspace creator is idle but other collaborators are not
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
We run a frequent Mob-programming meetup, where gitpod serves us very well for collaboration with low setup overhead for our participants.
It looks like the session times out if the workspace owner is idle for some time, even if the collaborators are actively using it.
In our sessions, sometimes the main collaborators are different users than the owner of the workspace (and the repo). It would be nice if also the activity of other users would be checked.
Steps to reproduce
- Start a workspace
- Share the workspace with somebody else
- Only interact with the workspace from the other user
- Session will time out after a while
Workspace affected
bronze-iguana-w9e78jfb
Expected behavior
It would be nice if the workspace owner doesn't have to restart the workspace.
Example repository
No response
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Reproduce the timeout by starting a shared workspace, having only a collaborator interact with it, and tracing the workspace idle-timeout behavior. Done means collaborator activity prevents the session from timing out while the workspace is in use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100