Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tracking: do more polling

Open
#2,867 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

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.

Description

customer

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.

https://github.com/oxidecomputer/console/blob/ef73c18e89a7b1f2bbe488a60fdc30b387e917fd/app/pages/project/instances/InstancePage.tsx#L149-L164

https://github.com/oxidecomputer/console/blob/ef73c18e89a7b1f2bbe488a60fdc30b387e917fd/app/pages/project/instances/InstancesPage.tsx#L138-L192

Dominant language
TypeScript
Stars
228
Forks
22
Avg merge
8h 35m
Merged PRs (30d)
22

Getting set up

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.

More from oxidecomputer/console

All issues in oxidecomputer/console

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.