Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,33 @@ and this project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.ht
path) are refused, and endpoint URLs print userinfo-stripped. The REPL prints
everything verbatim as before. No tool schema changed. `config set` of an
endpoint URL acknowledges with the userinfo-stripped value.
- Unbounded listings now crush to a row budget — first-40 + last-10 + top-severity
anomaly rows, exact-deduped, hard cap 100 — instead of dumping thousands of
rows into the client's context: `updates` (anomaly: non-`testing` status,
`failed`/`blocked` outrank the rest, unknown/missing/null status kept; narrow
with `--limit/--offset/--field/-G`), `list_refhosts` (anomaly: non-`free` lock
or pool claim, `locked`/claimed outrank the rest; narrow with
`--limit/--offset/--name/--arch/--product/--version/--addon`), and
`openqa_overview` (anomaly: non-`passed` version rows, `failed` outranks the
rest, build checks with matches; display only, `--export` still writes the
full overview; narrow with
`--no-aggregated/--aggregated-groups/--days/--test-pattern`). `--json`
over-cap stdout is a JSON envelope `{"rows": [...], "truncation": {...}}`
so stdout stays valid JSON (CLI and MCP alike; also in `--json` help).
Anomaly counts cover the full dataset and the notice omits
`(K/L anomalies kept)` when none exist.
Any middle slice is
recoverable via pre-crush `--offset`/`--limit` paging (chosen over an
explicit-window notice as it fits the existing `--limit` plumbing).
`list_refhosts --free` windows before probing, so paging reduces the SSH
probe cost; windowing order is the matched inventory order and the
footer stays pre-window totals. A pure window emits only a probe note
(`…[probed X of Y hosts; …]` human, `"probe"` object in JSON), never a
truncation notice with anomaly counts over unprobed hosts.
Row-cap is not byte-cap: MCP `max_output_bytes` can still cut mid-array on
huge rows; `openqa_overview` per-section caps sum to ~600 rows total.
**MCP schema note:** additive only — `updates` gains `offset`, `list_refhosts`
gains `limit`/`offset`; no renames/removals.

### Deprecated

Expand Down
1 change: 1 addition & 0 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading