Runners: Connectivity and Status columns, and a filterable queue issue #243 closed: completed andymccall opened this 19 days ago · 0 comments

A runner whose job slots are all full stops polling, so the hub marks it offline while it is mid-job (mars-1 on 2026-10-16, holding one metalgear2 job; earth-1 earlier with three). Offline should mean unreachable, not busy.

Andy's design (2026-10-16):

• Runners table: rename the current column to Connectivity (online / offline, from the runner's last contact), and add a Status column saying what it is doing: idle, or running N of M jobs (repository, job, for how long), draining.
• Status links to the queue: clicking a runner's status opens the Queue pane filtered to that runner.
• Queue filters: by repository, by status (queued / running / waiting / declined) and by runner, kept in the URL so a filtered view can be shared.

Underneath: a busy runner must still count as connected. Treat any authenticated call from the runner (log appends, heartbeats, finishing a job) as contact, or have the runner send a heartbeat while its slots are full, so Connectivity is true while jobs run.