Remove Functionality That Keeps Certain Failed Prebuilds
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
When prebuilds fail due to a users init tasks we currently keep the prebuild around incase the user wants to inspect them to potentially determine why it failed. After some discussion within the development teams it looks like the this functionality does create a bit of a problem in understanding the semantics of a large majority of users.
What we'd like to do here is simplify this and remove the partition state that is the result of these failed prebuilds.
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
No files, tests, or entry points are named. Start by locating the handling for failed prebuilds, user init tasks, and the resulting partition state; confirm the intended behavior with the linked internal discussion and identify tests that cover retained failed prebuilds before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100