bleedingdeacons / monitor / 33070385016
93%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 13
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 96.173% (+0.2%) from 95.953%
33070385016

push

github

web-flow 
feat: show who answered first, and offer Close instead of Acknowledge

A broadcast rings every certified handset at once, and whoever answers
silences only their own. Reach now sends a second message to everybody
else it went to, saying who picked it up. This is the half that reads
it.

**It never alarms.** Waking a second responder at three in the morning
to tell them the first one answered would be worse than saying nothing.
The notice is admitted like anything else so it can be read, but it
never reaches the alarm, and on Android it goes to a separate
reach_notices channel — a channel's importance and sound are fixed when
it is created and cannot be changed afterwards, so a quiet notification
posted to the alarm channel is not quiet at all. Windows drops the Alarm
scenario and the looping audio; iOS drops the alarm tone and the
time-sensitive interruption level, which would otherwise interrupt a
responder who has deliberately silenced their phone.

**It marks the alert it reports on.** That card gains an "Acknowledged
by …" line. Matched on the message uuid rather than the alert id,
because the id a notice could quote belongs to whichever copy the other
responder happened to answer — one message to somebody holding two
handsets is two alerts with two ids, and the uuid is the only thing the
copies share. Applied before the expiry and duplicate checks, like the
removal notice: a notice is a statement about the past that goes on
being true, not a stale emergency that has stopped mattering.

**It turns Acknowledge into Close** — on the notice, and on any alert
somebody else has already answered. Acknowledge means "I have this", and
neither of those is a job left to take on. The command is unchanged, so
closing still tells Reach this handset has dealt with the alert, which
is what stops it coming back on the next poll; it just no longer claims
something that is not this responder's to claim.

The handset still rings until somebody touches it. Silencing ... (continued)

955 of 993 relevant lines covered (96.17%)

18.49 hits per line

Coverage Regressions

Lines Coverage ∆ File
16
93.92
0.65% Services/AlertService.cs
Jobs
ID Job ID Ran Files Coverage
1 33070385016.1 13
96.17
GitHub Action Run
Source Files on build 33070385016