Commit Graph
2 Commits
Author SHA1 Message Date
alexm 75c1d466da A proved routine is not said to have run out of time
Build, test, deploy / site (push) Successful in 7m38s
In a container running the tests on two processors, the Quarto
gallery's proved example was rendered with the warning that time ran
out: the generated inputs that cross-check a proof had been cut short by
the 3-second clock, with every claim already proved. core 941af6b counts
that only where a claim is still open. The tests that hold what a proof
finds give it time to spare, and the browser-side request builder takes
prove-seconds as the Lua filter does.
2026-11-13 07:33:35 -05:00
alexm 7000662539 A proof's time limit is the reader's to set
Build, test, deploy / site (push) Successful in 7m44s
The Prove view gives each routine 3 seconds on the clock. On a slow or
busy device that runs out before the proof does, and claims stay open
with nothing to say why.

- The view says when the time, not the proof, stopped the checker, that
  what was not finished is open and not disproved, and offers to prove
  again with the next longer time. The setting is at the foot of the
  view: 3, 10 or 30 seconds or 2 minutes for each routine, kept in the
  browser (pplus.proveclock).
- A proof rendered with Quarto takes prove-seconds on the shortcode or
  pplus-prove-seconds for the site, and the render warns when the time
  ran out.
- The home page's own example is proved with no time on the clock, and
  the tests that hold a proof's outcome give it time to spare, so
  neither depends on the machine.
- core moves to 38e6e2c, whose report says which routines the clock
  stopped.
2026-11-13 07:01:35 -05:00