gitpod-io / gitpod-io/gitpod

Improve Page Displayed to User When a Workspace Cannot Start From a Snapshot Due to the Snapshot Not Existing

Open
#11,545 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

aspect: error-handling feature: pvc / snapshots meta: never-stale team: workspace type: improvement
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

Is your feature request related to a problem? Please describe

When I attempt to spin up a workspace using a snapshot URL that was provided to me and the snapshot does not exist I am shown an error about a timeout and "last backup failed: cannot find workspace during DisposeWorkspace.". I also see the 'Go to Dashboard' button and a 'Start Workspace' button. This isn't to helpful as clicking on the 'Start Workspace' button will not work and going back to my dashboard doesn't really resolve anything either.

Screen Shot 2022-07-21 at 13 01 57

Describe the behaviour you'd like

  • We should tell the user that the reason of the failure is because the snapshot does not exist.
  • Provide them with next steps on how to resolve the issue (create a new snapshot?).
  • Contact Support?

Describe alternatives you've considered

N/A

Additional context

Related conversation in Front.

Front logo Front conversations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation files or tests are named. Start by locating the frontend page used when a workspace fails to start from a snapshot, then trace how a missing snapshot is reported. Done means the page identifies the missing snapshot and provides appropriate next steps instead of timeout messaging and unusable actions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.