Skip to content

When a cloud integration token expires mid-session, we do not attempt to refresh it #4240

@axosoft-ramint

Description

@axosoft-ramint

Description

  1. Connect a cloud integration (like GitLab).
  2. Keep the current window open until the token expires (for GitLab, 2 hours)
  3. Attempt to use the integration (for example, view GitLab PRs in Launchpad)

At this point, we know locally that the session has expired because we have that info on it. But we don't attempt to check - we just attempt the call, get errors, and are not refreshing the integration properly until completely reloading VSCode.

Instead, we should check for expiration before running any call to the provider, and refresh if it's an expired cloud session.

GitLens Version

17.0.3

VS Code Version

No response

Git Version

No response

Logs, Screenshots, Screen Captures, etc

No response

Metadata

Metadata

Labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions