Artifact 2fbec586d9c4c6b4f24f2f1025b683a390cf92a095bf30cb4bae4fdd5a055756:
- File
internal/api/register.go
-
2026-08-26 11:24:13
— part of check-in
[a0fa952495]
on branch landing-merge
— ops: read the history back — a route across days
The store recorded renders and nothing read them. The panels are one process's memory, so the page could say how fast a route is now and never whether it is worse than it was — which is the question after a deploy.
The drilldown gains a per-day table from the store: p50, p95, max. Nearest-rank percentiles, matching how the snapshot computes them, so two numbers on one page both called p95 agree.
Empty for no traffic and empty for history-off are different answers and the page gives the right one. (user: dmestas, size: 267899) [annotate] [blame] [check-ins using]
- 2026-08-26 11:24:35 — part of check-in [23cec0f0fd] on branch trunk — Accepted. The link was in the DAG the whole time, and the history is finally being read. (user: dmestas, size: 267899) [annotate] [blame] [check-ins using]
-
2026-08-26 11:24:13
— part of check-in
[a0fa952495]
on branch landing-merge
— ops: read the history back — a route across days