Skip to content

YuCe 0.1.3

Choose a tag to compare

@OrganeticSphere OrganeticSphere released this 05 Nov 00:17
· 77 commits to main since this release

YuCe 0.1.3: fixes from an outside review of 0.1.2, and the results stated as far as they go.

Two independent outside checks rebuilt the project and recomputed the published tables from the recorded runs: the numbers match.
They also found defects in the command line and in how the results were presented. This release closes them.

Fixed

  • An unknown flag or a stray argument is refused. A typo used to switch a check or a limit off in silence:
    audit-verify --expct receipt.json printed VERIFIED without reading the receipt. Each command now names its flags and how many
    other arguments it takes; anything else exits 2 before the command runs.
  • apply exits 1 when a step is refused. apply && verify used to take a refused run for a sound one.
  • A journal whose end is no complete entry is no longer a clean pass. Without a receipt, audit-verify reports TORN_TAIL
    (exit 1). A resuming server still recovers, as it must after a crash, but says so at once and keeps the bytes beside the journal.
  • audit-verify on a file it cannot read exits 2, not 1. audit-serve binds its port before it creates the run.
    update-doc refuses a document the container does not have. The inspector page refuses a malformed report.

Changed in the texts

README and BENCHMARKS no longer present a count of comparisons won or the model calls after a withdrawal as a result. The numbers
stand, but the samples are small, most of those calls had nothing to do with the withdrawal, and the kernel's side makes more
calls. We claim no gain in answer quality. See "How far these numbers go" in BENCHMARKS.md.
LIMITATIONS now says plainly what a journal cannot show without a receipt.

Full list: CHANGELOG.md.

Assets

  • Binaries: yuce-v0.1.3-<target> for Linux x86_64, Windows x86_64 and macOS (arm64, x86_64), each with sbgk, its alias
    yuce, LICENSE, NOTICE, THIRD_PARTY_LICENSES.md and README; SHA256SUMS-<platform>.txt.
  • The recorded runs of BENCHMARKS section 1 stay in the v0.1.0 release.

Check a download with sha256sum -c SHA256SUMS-<platform>.txt.