Skip to content

Improve Gitpod timeouts for multiple clients (revise the 5 minute editor connection timeout) #10373

Closed
@loujaybee

Description

@loujaybee

Currently, a workspace will initiate a 5 minute timer from close of any active editor. This current behaviour assumes too much that the user is operating a single client connection. Gitpod should be smart enough to recognise when a user is making multiple connections and not time out when a user swaps between SSH, VS Code or JetBrains with a workspace.

However, in scenarios where there are two editors open, this timeout should not be triggered. Ideally, we initiate the timer from the last active editor, to prevent breaking workflows where two editors are used. We should also check: https://github.com/gitpod-io/website/issues/2144 - to ensure the timeout logic is fully documented.

See internal link [1]

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions