mesh-delivery

Files

T

jschoubben 07b5f13474 mesh-delivery-indexer reads a registered module again once its repository becomes readable, and takes one in on ask (issue 1945)

A registered module whose repository the forge answered 404 (car-hunter, snake, before the forge's account could read
them) was read again only when the indexer started again or the controller wrote a new build record of it, so the grants
part's composed user list stayed short of their subjects and the take-over was refused. A failed read now keeps the
module as unread, read again on the next source revision and the next merged message (no timer of its own), and the new
tool indexer_take_in (the tools bundle mesh-delivery-indexer-tools, through the indexer's takeins state, as the
builder's builder_ask_again) takes one in now and answers what it stored or why not.

2026-10-26 14:01:34 +01:00

mesh-delivery-assigner

Assigner: clear a stale hold's condition before taking its ask away, so a failed clear is retried at the next pass (issue 1906)

2026-10-26 11:03:09 +01:00

mesh-delivery-builder

Builder: count only deliverable asks ahead, drop the old message of an ask asked again, and read a seat's queue (issue 1945)

2026-10-26 01:19:30 +01:00

mesh-delivery-checker

checker_status reads the node-engine at its running commit, as the checker's decision does, so it stops listing every candidate as waiting for a trunk move (issue 568)

2026-10-26 13:25:18 +01:00

mesh-delivery-forge-bridge

Delivery parts: take the essential and optional bucket opens from mesh-sdk (issue 1945)