bluerobotics/cockpit

frontend: Alerter: use priority queue for alerts

Open

#2,303 opened on Dec 11, 2025

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Vue (55 forks)auto 404
enhancementgood first issuesafetyuxwidget-specific

Repository metrics

Stars
 (181 stars)
PR merge metrics
 (PR metrics pending)

Description

Current behaviour

Alerts get queued up FIFO, and displayed at speaking speed (since #2280), so if a collection of alerts appear in close sequence then a critical alert at the end could waste several precious seconds while the alerter speaks every alert before it.

Expected or desired behaviour

If we instead use a priority queue for the alertStore.alerts, where priority is determined by the alert severity, the most important alerts would always appear soonest, slowed down only by the one which is currently being read.

Prerequisites

  • I have checked to make sure that a similar request has not already been filed or fixed.

Contributor guide

Research direction
Modify the alert store to use a priority queue that orders alerts by severity so that critical alerts are processed first. Implement a priority queue data structure or use an existing library and integrate with the current alert processing logic.
Tech stack
vuejavascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptVuePriority Queue Data Structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55