Marc-André Bombeck 7dbec3bc4d feat(admin): name the status a failing provider came back with ...

The provider-health ledger has recorded the HTTP status of every failure
since v1.11.0 and nothing has ever read it. The operator card could say
three of five chains were failing without saying whose problem that was,
which is the one thing the operator needs: a 401 is a credential only they
can replace, a 429 or a 503 is the provider's afternoon and waiting is the
right move.

The fold carries the status of the failure whose instant the row already
shows, not an aggregate over the column. A MAX of two HTTP statuses is
arithmetic on a label, and a status describing a different failure than
the one on screen would send the operator to the wrong place. The column
joins the grouping key instead, and the fold picks the group belonging to
the newest failure.

Blank where there was nothing to record: a connection that never completed
has no status, and a chain that has since recovered had its status cleared
along with the rest of its failure state.

2026-09-03 06:05:58 +02:00

..

de.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00

en.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00

es.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00

fr.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00

it.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00

ko.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00

pl.json

feat(admin): name the status a failing provider came back with

2026-09-03 06:05:58 +02:00