14 lines
990 B
Markdown
14 lines
990 B
Markdown
# Diagnosis — 207
|
|
|
|
**2026-10-03.** The worker was deleted by hand and the controller, on restart, recreated it with the
|
|
server's default delivery policy — every message the stream holds — on a stream that keeps its history.
|
|
The build machine then took every ask since 1 October in order, and each outcome was taken in as news:
|
|
`takeIn` records the build and registers the manifest it carries, whatever commit it is from. Nothing
|
|
in the consumer derivation said where a seat's worker starts; nothing in the taking-in compared the
|
|
outcome's commit with what the catalogue already held.
|
|
|
|
Owner mesh-controller. Fixed in part: a worker re-made by the controller on a history-keeping stream
|
|
now delivers from the moment it is made (PR #233). Open for a decision, kept in the report's questions:
|
|
whether a seat's work queue should keep acknowledged asks at all, and whether an outcome for a commit
|
|
the catalogue has already moved past should be recorded but never registered or rolled out.
|