feat(frontend): add outdated indicator to runners#4446
Conversation
|
🚅 Deployed to the rivet-pr-4446 environment in rivet-frontend
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
PR Review: feat(frontend): add outdated indicator to runnersOverall this is a clean, focused frontend feature. The core logic is straightforward and the refactoring of the Bugs / Logic IssuesOutdated check masks offline runners The current priority order treats an outdated runner as more important than an offline one. A runner that is both outdated and offline will show the hourglass-clock icon, hiding the fact that it hasn't pinged in >15 seconds. An operator looking at the dashboard would not know the runner is unreachable. Consider either:
Unused Import
// Remove this — it is imported but never referenced
faTriangleExclamation,Icon Semantics
Minor NitsTooltip layout inconsistency The outdated badge <div className="text-center relative size-8 flex items-center justify-center">The other badge
Summary
The refactoring of the status badge |

Description
This change adds version tracking and outdated runner detection to the runners table. The implementation calculates the latest version across all runners and displays a warning status for runners that are behind the current version. The status badge logic has been refactored to prioritize outdated runners, showing them with an hourglass clock icon and red styling before checking ping status or RTT performance.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: