Repository navigation
v0.13.1: a provider's pre-session refusal is typed, the operator names how a stopped run ended, and the dsh console reads its fleet a page at a time
v0.13.1 is a patch on
v0.13.0 “Járngreipr”. It carries the fixes that were in
flight when 0.13.0 shipped, and the changes merged beside them. It
includes everything merged since
v0.13.0.
It needs no migration. Read
Upgrade and compatibility if you run a
driver of your own or a recipe that resumes runs across the upgrade.
What changed
- A provider's pre-session refusal is typed (decision 0103, slice 4a;
#992).- The refusal. A refusal before a session starts is a closed class,
rate_limitorother. It carries the provider, the route, bounded
words, and optionalstatusandretry_after_seconds. - The contract. It reaches the engine on the driver's result under
the new extension schemadriver-refusal.v1, which is additive at
driver protocol v1. A present refusal is never read as absent. - The probe. A driver that advertises
capabilities.probecan be
sent a probe, which stops at the model's first answer. - dsh's startup refusal is kept on every path. A stopped,
interrupted, incomplete or unreadable capture of dsh's startup error
output no longer loses the refusal: an incomplete or unreadable capture
refuses the start by name. - Nothing waits on the refusal yet. #430's later slices turn a provider's
rate limit into a cool-down instead of a park.
- The refusal. A refusal before a session starts is a closed class,
- The dsh console reads each hearth's fleet a page at a time (#907;
#990,
#995).- Paged fleet reads. A hearth's fleet is read 100 runs at a time,
with anN+count where more exist, and "show more" extends one hearth. - One run on its own.
brokkr runs --json --run <id>prints that
run's row, at view version 28. - One gate publishes world data, and it holds the console's only
writer. Everything the console paints is fenced by the journal and the
map it read.
- Paged fleet reads. A hearth's fleet is read 100 runs at a time,
- The operator names how a stopped run ended (decision 0064, slices E1
and E2; #988,
#1002).- The vocabulary. A run's ending is one closed word that brokkr-core
derives from the ruling that ended it. brokkr operator --run <id> classify --cause <cause>. Names how a
stopped run ended:superseded(with--by-run),infrastructure,
delivered-elsewhere(with--by-ref),withdrawn,exhaustedor
operator-stopped.- The contract. The annotation is recorded under the new payload
schemaoperator-ending.v1. A completed run is never classified, and
the fold reads none of it, so a classified run folds byte for byte as
before.
- The vocabulary. A run's ending is one closed word that brokkr-core
Fixed
- Flaky tests that could drop a pull request from the merge queue:
- a heap peak is the measuring thread's alone, so another thread's
allocation cannot move a same-peak equality, on Linux and on macOS
(#979); - a test that re-runs its own binary captures the child's output, so the
child's test summary cannot interleave with the parent's
(#996); - a protocol test whose verdict depended on another test's stray
process now runs in an engine of its own
(#1001).
- a heap peak is the measuring thread's alone, so another thread's
- macOS CI time: the large run-page tests build their journals once per
binary (#985), and
the macOS tests are spread over four machines
(#983,
#999). - The flake's digests match v0.13.0
(#984).
Upgrade and compatibility
- Drivers of your own.
driver-refusal.v1is an extension: a driver
that sends no refusal is read as before. A driver that advertises
capabilities.probemust stop at its first model answer. - Engine version. Bundle digests cover the engine version, so a run
started under 0.13.0 resumes only under 0.13.0's binary.
Known issues
- A masked refusal can grow past its 300-character bound when a bound
secret's name is longer than its value. The attempt then fails closed,
as an unreadable refusal, and no secret is disclosed. The fix is in
progress: #991. - A paged run read over a run with about 66,000 checkpoints takes
about 0.3–0.6 s on a release build, where #753 aims at milliseconds.
About 94 ms of it is the chain verification at opening:
#994. - Every known issue listed in v0.13.0 still
applies.