jzombie / rust-argtuner / 38482464960

76%

Build Type

push

github

Committed by web-flow

Commit Message

feat: Watch live trial streaming, output robustness, and promotion lineage (#24)

## Changes

- Bump term-wm to v0.10.15-alpha (`term-wm`, `term-wm-console`, `term-wm-core`, `term-wm-render`, `term-wm-ui-facade`)
- **Echo fits the live viewport:** echoed fragments carrying the erase sequence (transient `\x1b[2K` progress-bar redraws) are cut to the live terminal width, re-queried per write so resizes apply immediately. Without this, an over-wide redraw wraps to two rows and the next in-place erase clears only one, eating line heads. One-shot `\r` records and plain `\n` lines pass whole, as does everything when piped/logged. Display-only: stored output and the live-parse callback keep every byte, with no width contracts on any platform. Width-aware children truncate bars to it instead of emitting wrap-prone lines.
- **Split multibyte decoding:** the stream reader decoded each read with `from_utf8_lossy`, emitting U+FFFD for any multibyte sequence straddling two reads — corrupting non-ASCII bar text and any split multibyte inside protocol JSON (a dropped event). Reads now decode incrementally, retaining truncated trailing sequences for the next read.
- **Promotion lineage in `watch`:** trial rows now carry their config/rung (`cfg=c r=r/b`), the details pane shows the full promotion chain (`t3(r0, ok) → t5(r1, ok) → t8(r2, error)`, selected trial marked), and metric charts chain same-config trials up to the selected rung into one continuous curve (arrival-position x, never folded). Previously every rung rendered as a disconnected trial restarting at x=0, making halving progress unreadable.
- **Live trial updates in `watch`:** the subprocess runner now invokes an `on_line` callback once per complete stdout line, and the trial evaluator stream-parses `::ARGTUNER::` events as they arrive — `model.epoch_end` rows reach `trials.sqlite` per epoch and throttled `model.step_end` rows reach the DB and the TUI step publisher about once per second, instead of every... (continued)

Coverage Stats

715 of 968 new or added lines in 7 files covered. (73.86%)

3 existing lines in 2 files now uncovered.

8862 of 11682 relevant lines covered (75.86%)

2051078.06 hits per line