wai-quantum-service: a job the service was running when it stopped runs once more #613

Merged

dcharlot merged 1 commit from wai/quantum-service-rerun into main 2026-11-04 12:10:52 -05:00

Conversation 0 Commits 1 Files changed 16 +305 -64

2026-11-04

Transaction Science

wai-quantum-service: a job the service was running when it stopped runs once more ...

A job that was running when the service stopped came back interrupted,
its request kept, and nothing ran it again unless its client sent it
again. Since the engine gives the same result for the same request, the
service now runs it again itself: on start, a job that was running is
queued again in its order, to run once more from its stored request, and
its `interruptions` say when the service stopped. Stopped again while it
runs once more, it comes back interrupted with the reason and is not run
a third time (RERUNS = 1), so a job that stops the service whenever it
runs does not run for ever. GET /v1's `restored` counts the jobs run
again.

wai.quantum.job/1 now lists `interrupted` among its statuses, which the
service has returned since its jobs were kept across restarts, and the
optional `interruptions`.

Also: the store's pseudonym test held the hex of a keyed hash to not
containing "203", three digits of the address, which a random key gives
about once in 140 runs. It now holds it to hex, which cannot spell the
address.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1b07caf646

• View at this point in history

2026-11-04 10:27:04 -05:00