Backend down is not Braid's status: a dot for the server, and backend cells that outlive the run #391

Closed
opened 2026-11-05 00:08:25 -05:00 by cmoriarty · 1 comment
Owner

What happens

  • The top bar's Braid box reads Backend down in red. A run's backend isn't Braid's status, and it says so on every page.
  • A finished run's bar has no Backend or Model cell. /api/backends lists only live runs, so the cells go when the run ends, whatever the backend is doing.
  • Planning and Repair can use other backends, and the bar never says.

Fix

  • Braid box: a dot for the Braid server only. Mint green when it answers, yellow for a late or unexpected answer, red when it's down. No Backend down. This reverses #387, whose reason goes once the word does.
  • Run bar: one cell reading vLLM qwen3.8-27b, for any run, live or finished, with the same dot and an info hover.
  • Planning and Repair: their own cell when they differ. Otherwise the one cell's caption names them: Backend Planning Repair.

Done when

  • With vLLM down, the Braid dot stays green and the run's cell goes red.
  • A finished run still shows its backend.
  • A run with a separate Planning backend shows two cells.

Reported by the owner from the console, on run 172.

**What happens** - The top bar's Braid box reads `Backend down` in red. A run's backend isn't Braid's status, and it says so on every page. - A finished run's bar has no Backend or Model cell. `/api/backends` lists only live runs, so the cells go when the run ends, whatever the backend is doing. - Planning and Repair can use other backends, and the bar never says. **Fix** - **Braid box:** a dot for the Braid server only. Mint green when it answers, yellow for a late or unexpected answer, red when it's down. No `Backend down`. This reverses #387, whose reason goes once the word does. - **Run bar:** one cell reading `vLLM qwen3.8-27b`, for any run, live or finished, with the same dot and an info hover. - **Planning and Repair:** their own cell when they differ. Otherwise the one cell's caption names them: `Backend Planning Repair`. **Done when** - With vLLM down, the Braid dot stays green and the run's cell goes red. - A finished run still shows its backend. - A run with a separate Planning backend shows two cells. *Reported by the owner from the console, on run 172.*
Author
Owner

Shipped in PR #394, production 382c998.

  • The Braid box has one dot, for the Braid server only: mint green on time, yellow for a late or unexpected answer, stopped live updates or a problem with itself, red for no answer. No Backend down. This reverses #387.
  • One cell reads vLLM qwen3.8-27b, for any run, live or finished, with the same dot and an info hover. Planning and Repair share its caption, or have a cell of their own when they differ.
  • The strip meets the line above it and reaches both edges, and its captions are not in capitals. BRAID keeps its capitals, as the wordmark reads.

The cause of the missing cells: /api/backends lists only live runs, so a finished run lost them whatever vLLM was doing.

Evidence, on production just after the deploy, with vLLM really down: run 172's bar reads Backend Planning Repair, vLLM qwen3.8-27b, state down, why It is not answering (ConnectError), and the Braid dot is ok. That is this issue's done-when, on the real thing.

Also tests/api/test_run_backends.py, ui/src/components/chrome.test.ts, and new journeys in ui/e2e/backends.spec.ts. One of those tests caught a Planning backend on another server taking the wrong profile's name, now fixed.

Not proved: that the journeys fail on the old build, as they were not run against it. No real run on a separate Planning backend has been seen in the bar; that layout was read with a faked route, and its grouping is held by backend tests.

**Shipped** in PR #394, production 382c998. - The Braid box has one dot, for the Braid server only: mint green on time, yellow for a late or unexpected answer, stopped live updates or a problem with itself, red for no answer. No `Backend down`. This reverses #387. - One cell reads `vLLM qwen3.8-27b`, for any run, live or finished, with the same dot and an info hover. Planning and Repair share its caption, or have a cell of their own when they differ. - The strip meets the line above it and reaches both edges, and its captions are not in capitals. `BRAID` keeps its capitals, as the wordmark reads. **The cause of the missing cells:** `/api/backends` lists only live runs, so a finished run lost them whatever vLLM was doing. **Evidence, on production just after the deploy, with vLLM really down:** run 172's bar reads `Backend Planning Repair`, `vLLM qwen3.8-27b`, state `down`, why `It is not answering (ConnectError)`, and the Braid dot is `ok`. That is this issue's done-when, on the real thing. Also `tests/api/test_run_backends.py`, `ui/src/components/chrome.test.ts`, and new journeys in `ui/e2e/backends.spec.ts`. One of those tests caught a Planning backend on another server taking the wrong profile's name, now fixed. **Not proved:** that the journeys fail on the old build, as they were not run against it. No real run on a separate Planning backend has been seen in the bar; that layout was read with a faked route, and its grouping is held by backend tests.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#391
No description provided.