oxidecomputer / oxidecomputer/console
Handle error with creating and attaching disk to running instance
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
This might be too niche to bother with – but if you create and attach a disk to a running instance (lets say an instance is started separately from the tab you're in). The form submits successfully and you get both a success and failure toast, since it was created but not attached.
This might be a case for the multi-request modal pattern I worked on for affinity / image upload. The behaviour is the same, but its just clearer what's gone wrong.
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 locating the multi-request modal pattern used for affinity or image upload, then trace the disk creation and attachment flow for a running instance. Reproduce the form submission and verify that the UI reports the partial failure clearly without showing contradictory success and failure toasts.
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
- 45/100