gitpod-io / gitpod-io/gitpod

No Button to Start Workspace When In-Progress Prebuild Finishes

Open
#13,807 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature: prebuilds meta: never-stale team: webapp type: bug type: improvement
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

Bug description

When a user goes to start a new workspace and a prebuild is in-progress for the context the user will see a 'prebuild in-progress' screen. When the prebuild finishes no button or option shows to then start up a workspace from that prebuild. Even refreshing the page may not show the prebuild has been completed, they may instead see that a new prebuild has been started and thus the cycle continues.

Steps to reproduce
  1. Setup a project for a context.
  2. Make some commits and pushes that will result in prebuilds kicking off.
  3. Attempt to start a new workspace from prebuilds that are in-progress.
  4. Observe you see the prebuild in-progress page.
  5. Observe when the prebuild finishes that there's no button to then start a workspace from that prebuild.
Workspace affected

No response

Expected behavior

I would expect that once a prebuild is finished I see a button or option that then lets me start a new workspace from that prebuild.

Example repository

No response

Anything else?

No response

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

Reproduce the prebuild-in-progress screen using the listed steps, then trace the workspace-start flow that renders it. Check what happens when the prebuild finishes and after refreshing the page. Done means a clear option appears to start a workspace from the completed prebuild without repeatedly starting another prebuild.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
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.