Some prebuilds are not properly linked to their project
Open
Nobody has claimed this yet.
component: server
feature: prebuilds
meta: never-stale
team: webapp
type: bug
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Some incremental prebuilds link back to an non-existent (unknown) base prebuild.
For example:
- Incremental: https://gitpod.io/t/gitpod/gitpod/493e214f-b816-4d55-b98d-5b414d5d35fe
- Base: https://gitpod.io/t/gitpod/gitpod/a39f6aa4-3c6d-4447-9e44-40411b38152b
See relevant discussion (internal). Cc @jankeromnes
| Incremental Prebuild | Base Prebuild |
|---|---|
 |
 |
Steps to reproduce
N/A
Workspace affected
No response
Expected behavior
No response
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
Start by tracing how incremental prebuilds resolve and display their base prebuild, using the linked incremental and base examples as reference. Confirm where the base relationship becomes unknown and define the fix by ensuring incremental prebuilds link to an existing project prebuild; no source file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100