stroblmeandClaude Opus 5
f370601aec
Docs / docs (push) Successful in 27s
Playwright Tests / test-playwright (1, 2) (push) Failing after 18m28s
Playwright Tests / test-playwright (2, 2) (push) Successful in 5m11s
pre-commit / pre-commit (push) Failing after 2m2s
Test Backend / test-backend (push) Failing after 2m32s
Compose Smoke Test / test-compose (push) Successful in 32s
Playwright Tests / merge-reports (push) Successful in 5m50s
`space` ticks runs on the serve dashboard's table and `enter` compares them: one metric in braille, five distinct hues, and the table of what actually differs under it. Both halves are routes that already existed — the browser's own comparison endpoint for the curves, the runs export for the table, whose input columns are filtered to the ones that vary. The palette is hue rather than the web's lightness ramp on purpose: five steps of one brand hue collapse to a single colour on a 16-colour tty. The screen also subscribes to the engine's event bus over the same websocket a browser uses, so a run that starts and finishes inside a tick is seen rather than only recorded. `a` lists what a run left behind and fetches it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014SmyLMSqcJQ8tUL2qLj21s
15 lines
616 B
Python
15 lines
616 B
Python
"""The dashboard `fluksio serve` opens at a terminal.
|
|
|
|
A supervisor, not an engine: it starts `serve --plain` as a child and talks to
|
|
it over the same HTTP API and the same websocket every other client uses. So
|
|
the engine is a process that can be stopped and started under the screen
|
|
watching it, an engine somebody else started can be adopted rather than
|
|
duplicated, and quitting the dashboard is not the same as stopping the engine.
|
|
|
|
Nothing of the engine is imported here — that lives in the child.
|
|
"""
|
|
|
|
from fluksio.tui.app import ServeApp, child_argv, run_tui
|
|
|
|
__all__ = ["ServeApp", "child_argv", "run_tui"]
|