Skip to content

v0.15.0 “Gullinbursti”: `brokkr dispatch` stands and starts queued runs every interval until told to stop, a driver reaps the orphans its harness leaves, and a dry sweep names what a pass would keep

Choose a tag to compare

@github-actions github-actions released this 19 Nov 02:54
· 53 commits to main since this release
v0.15.0
e4a5314

Gullinbursti is the golden-bristled boar that Brokkr forged. It runs
over sky and sea, by day and by night, and its bristles light the dark.
This release is about the work that keeps going while nobody watches:

  • The dispatcher stands. brokkr dispatch repeats its pass every
    --every seconds and starts what admission admits, until a signal
    tells it to stop. Decision 0110 is built, and with it decisions 0095
    and 0068.
  • A driver reaps what its harness leaves. A seat whose tools leave
    orphaned processes no longer piles them up as zombies under its driver
    for the rest of the attempt.
  • A dry sweep tells the whole truth. brokkr sweep --dry-run names
    the trees a pass would keep, with the pass's own reason.

It includes the changes merged since
v0.14.1.

It needs no migration. Read
Upgrade and compatibility if a script
relied on brokkr dispatch without --once being refused, or if you
build against Brokkr's crates.

What changed

  • brokkr dispatch stands (decision 0110, slice 6c;
    #1140).
    • The loop. Without --once, brokkr dispatch runs one pass, prints
      the pass's report, reports the drivers that have exited since, and
      sleeps for --every seconds less the pass's own duration. Each pass
      reconciles first. --every is 5 to 3600 seconds, and 60 unless set.
    • A stop. The first SIGINT or SIGTERM wakes the sleep at once. The
      entry in flight still gets its spawn row and its driver. Nothing is
      claimed after the stop, and the dispatcher exits 0. A second signal
      ends it at once, with 128 plus the signal's number. The next
      dispatcher's reconciliation then settles anything left in flight.
    • Drivers are never signalled. Each runs in a session of its own and
      is reaped between passes. A driver that dies while its run reads
      running gets a line with the command that resumes the run as it was
      queued: brokkr dispatch drive --entry=<entry> --claim=<claim> --db=<journal>. The drivers still running when the loop ends are
      named, and left running.
    • Its endings. A pass's ending ends the loop and exits non-zero, in
      the same words --once prints: a fence-out, a replaced binary, a
      store error, or a tick whose report cannot be written.
    • The guide. Running the dispatcher
      covers what a tick does, and running the dispatcher under a systemd
      user unit (KillMode=process) or a launchd agent. It says what each
      ending leaves and how to recover it, including after the host goes
      down.
    • Built. Decisions
      0110,
      0095 and
      0068 now read built.
  • A driver reaps the orphans its harness leaves
    (#1133;
    #1148).
    brokkr driver is made its harness tree's subreaper, so
    the orphans of a seat's tools are adopted by it. It now reaps them.
    • The cause. One claude seat's driver held 156,752 zombies after a
      timeout-killed cargo test in its harness, until its attempt ended.
    • The reaper. While a driver serves on Linux, a reaper reaps each
      zombie it adopted, per pid, after two sightings of one identity.
      Reaping is best effort, and never ends an attempt or changes its
      result.
    • The door. Every child the driver spawns goes through one door,
      which registers it under the reaper's own lock as it is spawned. A
      harness that exits at once is never reaped out from under its handle,
      and its exit status is the one the driver reports.
    • The release. A child's hold is released by its own handle's wait.
      A pidfd the kernel will not wait on is closed, and a reaper the host
      refuses leaves nothing held.
    • The engine's own reap is unchanged. On macOS there is no subreaper,
      and nothing changes.
  • brokkr sweep --dry-run names the hands trees a pass keeps (5c2's
    follow-ups F3 to F5;
    #1142).
    • The kept half. A dry run now lists the lockless hands trees a pass
      would keep, with the pass's own words. The listing and the reaping
      share one reading of the same candidates, so the two cannot disagree,
      and the listing removes nothing.
    • One home for a refusal's words. A tree walk's refusal is worded by
      TreeError::cause alone.
    • Typed payload reads. The sweep reads effect/succeeded,
      operator/commanded and operator/accepted through typed decodes. A
      payload that does not decode keeps the run's rows, with the reason
      reported; it never panics.

Fixed

  • The coverage shard runner finds the pinned nightly's test binaries
    (#1147, closes
    #1129).
    The
    nightly puts them in build/<package>/<hash>/out/, so the per-binary
    bound never started a clock. It now judges a binary by its file name.
  • The cool-down readout is one narrow scan
    (#1138, closes
    #1112).
    The
    readout behind the fleet listing and the console read the table squared,
    one correlated statement per row. It now reads one narrow scan in one
    snapshot.
  • The park-cause design test names its cause when it fails
    (#1146, closes
    #1132).
    A
    failure printed a bare unwrap on None; it now prints the journal the
    test read. It is tests only.
  • brokkr-store's slowest tests plant their journals in one transaction
    (#1141, closes
    #1130).
    The
    ordinal test took nearly an hour on a SATA disk, one synced commit per
    event. It is tests only.

Upgrade and compatibility

  • brokkr dispatch without --once stands where 0.14.1 refused it.
    A script that ran the bare verb to check that dispatching is off now
    starts a dispatcher. --every beside --once is refused.
  • The crates' API moves.
    • brokkr-runtime: dispatch::stand, Stand, Stopped, Tick,
      Exited, Reaped and Ending::Unreported are new. Seams and pass
      take a third parameter, claims, read before each claim.
      admission::Room::claim is no longer public.
    • brokkr-protocol: hands::list_reapable_under returns a Listing of
      the reapable trees and the kept ones, and TreeError::cause is public.
  • Contracts and storage. The engine, event schema, database schema,
    queue storage and driver protocol versions are unchanged.
  • Engine version. Bundle digests cover the engine version, so a run
    started under 0.14.x resumes only under 0.14.x's binary.

Known issues

  • brokkr-runtime's library tests can fail one engine test per run at
    high test-thread counts
    , for example 128 on a 128-core host. A running
    driver ends with the wrong effect. Main fails the same way, so this is
    interference between tests, not slowness
    (#857). Run
    them on about 24 CPUs.
  • brokkr doctor's version probe has no time bound, and its tests run
    the host's tools under a temporary HOME.
    On a host with Volta-installed
    Node tools, a shim there can call itself without end
    (#1137).
  • The dispatcher's started: line names no driver log path, and the
    standing loop reads its stop every 50 ms rather than waking on the
    signal. Both are carried from 6c's review.
  • The known issues listed in v0.14.1 that
    this release does not address still apply.