Skip to content

sift 1.27.2 — the browser build compiles again

Choose a tag to compare

@jjba23 jjba23 released this 12 Nov 14:32
· 45 commits to trunk since this release
9ef9819

Fix

  • The browser build compiles again. The deploy job of v1.27.1 was the first thing to build the Wasm module since the index work landed, and it stopped at make-deadline: get-internal-real-time and internal-time-units-per-second are (guile) names that the target's (guile) does not bind. A core that compiles under Guile therefore stopped the browser build by name half way through — the failure mode web/README.org describes, found by the deploy job rather than by a test.
  • The clock is R7RS's (scheme time) now. current-jiffy and jiffies-per-second are the portable spelling of the same question, monotonic, and answered by both implementations without a shim. (ice-9 time) and (srfi srfi-19) were the obvious alternatives and neither works: both reach for the same missing names. Nothing else changes — a deadline is still a moment, and the bound is still kept by not starting work that would pass it.
  • The comment says it without naming a target. tests/web.scm keeps the seam (no file under src/sift/ may name the browser, Wasm or Hoot), and a comment is a file's text: the first attempt broke that test, which is the test doing its job.

Continuous integration

  • maak-web moved into the gates. It was only ever run by deploy, which runs after the merge, so the class of failure no Guile-side test can see — a name the Wasm target lacks — reached the trunk. The gates compile the browser build on the pull request as well as on the push now, and it costs a compile the deploy job was paying for anyway.

Verification

  • maak release 1.27.2 ran every gate before the commit: docs, test, check, self-check, fixture-check, emacs-check, emacs-test.
  • Veritas suite: 105 tasks, 153 seconds, no failures. ERT suite: 31 tests, 0 unexpected.
  • sh web/build.sh writes sift.wasm (3.1 MB) and the page's three requests — version, lint, format — answer through Hoot's runtime under Node, so the module loads and runs, not only compiles.
  • make-deadline still behaves: a 100 ms deadline is in the future, a 0 ms one has passed.

🤖 Generated with ECA (deepseek/deepseek-flash)