oxidecomputer / oxidecomputer/console
Tracking: do more polling
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
Polling on instance list and detail feels quite good, so we should probably do it in as many places as possible. I think we want to make it fairly automatic so it's not bespoke on every page. The polling logic on the instance list is non-trivial, and we'll probably want to abstract something out of that that lets us do similar things on other pages, specifically polling faster when items are in states we consider transitional and therefore likely to change soon.
A good page to test this on is the snapshots page after creating a snapshot.
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 reading the polling logic in app/pages/project/instances/InstancePage.tsx and InstancesPage.tsx at the linked sections. Compare how polling behaves on the instance list and detail pages, then investigate the snapshots page after creating a snapshot. Done means a reusable, largely automatic approach supports polling across pages and responds faster for transitional states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100