Skip to content

v0.15.2: a journal path is always the literal file it names, a dsh 0.2 transcript that ran background jobs reads again, and a volta shim under a private HOME no longer recurses

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 17:24
· 23 commits to main since this release
v0.15.2
659aed4

v0.15.2 is a patch on v0.15.1. It carries the two fixes
v0.15.1 held for it, and the changes merged beside them. It includes
everything merged since
v0.15.1.

It needs no migration. Read
Upgrade and compatibility if you pass
--db :memory: or an empty --db, open a journal through a file: URI,
or match brokkr --help by its text.

What changed

  • Every journal path opens the literal file it names
    (#954,
    #1161).
    • Before: the bundled SQLite is built with URI filenames on. A
      --db such as file:other.db?mode=rwc opened, or created, the file
      the URI named, not the path Brokkr had checked and shown.
    • Now: both of the store's opens make the path absolute before
      SQLite sees it, so a file: path is an ordinary file name. Backup and
      restore read the same home.
    • Refusals name the path you gave. A path holding a nul byte is
      refused where you wrote it.
    • SQLite's two special names are no exception. --db :memory: is
      the literal file ./:memory:, and an empty path is refused. This is
      decision 0100's addendum, accepted by the operator.
  • A dsh 0.2 transcript that ran background jobs reads again
    (#1176,
    #1186).
    • Before: a session.v4 seat log from dsh 0.2.1-rc.2 that used the
      background-job tools carries job/registered and job/settled rows.
      Version four did not name them, so brokkr transcript refused the
      whole log as unsupported-format.
    • Now: those two kinds, and working-directory/change, are quiet
      bookkeeping under version four. A job's output still reaches the
      transcript through tool/result.
    • A catalogue fixture: the 34 record kinds seen across 589 dsh
      0.2.1-rc.2 transcripts are a test fixture, and every kind in it must
      be placed. Decision 0086 ruling 4 (proposed) names the three kinds.
  • A volta shim under a private HOME no longer recurses
    (#1136).
    • Before: the unboxed dispatch and the harness probe clear the
      environment, keep the engine's PATH and set a private HOME. A
      volta shim then looked for its home under that empty HOME, fell
      back to node on PATH, which was the shim again, and recursed until
      fork failed.
    • Now: one resolver tells the child the volta home its PATH
      reaches: the engine's own VOLTA_HOME, else ~/.volta, but only
      when PATH lists its bin. The workspace box is unchanged.
    • Decision 0111 records the rule.
  • brokkr --help cites no decision, ruling or issue
    (#1170,
    #1173).

    Every help line that cited one says, in plain words, what the citation
    meant. A test walks the whole command tree and refuses a citation. No
    flag, verb or default changed.
  • brokkr watch's plain frame paints its graph as the console does
    (#1168,
    #1174).
    The
    frame printed without a terminal, or with --no-view, now classes each
    node by the console's function and reads the same colours and glyphs.
    One run no longer reads in two colour schemes.

Fixed

  • The store's one append door inserts through the connection's
    statement cache,
    and the test fixture planter seals through it rather
    than a copy. A 20,000-event plant takes about 11 s, where the uncached
    insert took about 36 s
    (#1156,
    #1179).
  • Six more refusals are typed, with their text unchanged byte for
    byte:
    the transcript module's refusals, the dsh home's "no harness
    home", the secret store's write path, Muninn's unusable report, the
    composite pnpm reader's flow map and packages key, and the bundle's
    pinned-script admission. Their tests now match variants, not
    substrings
    (#353;
    #1182,
    #1183,
    #1184,
    #1188,
    #1189,
    #1197).
  • The capability broker's deadline proofs wait on the broker's own
    startup deadline,
    a hang is killed with its whole tree at the guard,
    and the teardown proofs are bounded
    (#1008,
    #1172).
  • The cool-down test fixtures plant their waits an hour past the
    clock,
    so a lock stall at 128 test threads no longer loses a test's
    own row
    (#857,
    #1175).
  • The shard runner's --help test reads the help at a width it fixes
    itself,
    so a narrow terminal no longer splits a path in it
    (#1181,
    #1185).
  • The flake's digests catch up with v0.15.1
    (#1171).

Upgrade and compatibility

  • --db.
    • A file: URI is now a file name: --db file:other.db?mode=rwc
      opens a file of that literal name, not other.db.
    • --db :memory: is the file ./:memory:, not a private in-memory
      database.
    • An empty --db is refused.
    • An ordinary path opens the file it opened before.
  • brokkr --help's text changed where it cited a decision, ruling or
    issue. Anything matching those lines sees the plain words instead.
  • The public API: unchanged.
  • Contracts: unchanged. The engine version reads 0.15.2.

Known issues

  • Three flaky tests are open, all seen only under heavy parallel load:
    • hands::session::tests::the_listing_removes_nothing_and_counts_what_the_reaping_would
      (#1157);
    • engine::broker::admission::tests::recovery::a_moved_head_end_keeps_its_attempt_reserved
      (#1164);
    • the hands:: box tests beside probe:: at 16 threads. A test's
      stand-in bubblewrap leads the shared PATH and reaches its
      neighbours. The cause is in the test support, not in the box
      (#1187).
  • Not in this release: brokkr graph's states and rules as aligned
    tables
    (#1167) is
    still in review.