mrhid6 7e1d67dba4 fix: file live outages as active, refuse "operational" over zero components
- A derived monitor outage with no `resolved_at` went to `History`, so an
  ongoing disruption was listed under "Past incidents" while the component pill
  beside it read Down. Unresolved now goes to `ActiveIncidents`.
- `overallState` returned `up` when nothing was counted: "all systems
  operational" claimed from no evidence at all. A page with no components now
  reports `no_data`, which the view already renders as "Status unknown".
- `EnsureStatusPageIndexes` returned on the first failure, so a transient
  failure on the `status_pages` index left `status_incidents` with no unique
  `(instance_id, incident_id)` index — a correctness property, not a scan
  optimisation. All three are attempted and the failures joined.
2026-08-25 09:04:54 +00:00
2026-08-24 12:17:46 +00:00
2026-08-25 08:44:38 +00:00
2026-07-24 09:51:30 +01:00
2026-07-28 15:07:19 +01:00
2026-07-29 10:35:07 +01:00
2026-08-11 15:03:03 +00:00
2026-08-25 08:44:38 +00:00
2026-07-28 10:30:29 +01:00
S
Description
No description provided
9.7 MiB
Languages
JavaScript 63.9%
Go 19.3%
TypeScript 16.6%