8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ce7d60cb6e	Merge pull request 'The delivery view reads only the keys a call names, in parallel, so node_haves and assigner_wants answer within their time (issue 1945)' (#52) from fix/view-reads-fast into main ... Reviewed-on: #52	2026-10-25 22:03:21 +00:00
jschoubben	41f25d3129	Read only the keys a view tool needs, in parallel, so node_haves and assigner_wants answer within the call's 30 s ... On 2026-10-25 node_haves and assigner_wants timed out at 30 s four times, even narrowed to one node and one module, while assigner_want answered at once. Each listed every key of its bucket and then read every value one after the other, filtering only afterwards; every value is a round trip from the tool through the runtime to the bus, which opens the bucket and gets the key, so a few hundred keys outlasted the call. Now a node and a module read that one key directly, a node or a module alone filters the keys before any value is read, and the values are read sixteen at a time, at most 1000 a call, the answer saying when it was cut. indexer_modules, indexer_candidates and builder_builds read their values the same parallel way. The kind: a read tool that reads a whole bucket key by key; every list tool of the view is covered.	2026-10-25 22:33:02 +01:00
jschoubben	4628ba26b4	Delivery parts: take the essential and optional bucket opens from mesh-sdk (issue 1945) ... The open helpers were copied into seven parts; code shared between modules lives in mesh-sdk, so they are mesh-sdk process's now and the parts are pinned at fix/1945-optional-buckets (e0d1de04), moved to its main once it merges, one delivery group with mesh-sdk.	2026-10-25 22:30:22 +01:00
jschoubben	eaf27f36af	Write a module's value only when the module changed, so a merge no longer rewrites every module of its repository ... The operator, 2026-10-25: only if a module has a new version in commit x is a new value written naming commit x. A merge wrote every module of the repository at the new commit, fingerprint unchanged (about 186 keys per mesh-catalog merge), and the controller's take-in took each in again: twice tonight it flooded. Now a merge that gives a module the value it holds but for the commit writes nothing, and the value keeps the commit its fingerprint first appeared at. The kind: a write that differs only in where it was computed. The other instance, a source revision re-stamping Src on every module at its repository's head after any merge anywhere, now stamps Src once. The trunk head stays the gate's source.main.	2026-10-25 21:13:59 +01:00
jschoubben	4fd6b934c8	Read the assigner's wants, differences and the haves with tools, so the gap between wants and sends can be read live (issue 1906 D1)	2026-10-24 16:19:42 +02:00
jschoubben	16ca51dc1f	Bound builder_builds by key prefix, limit and read budget, list unreadable keys, refuse fp2 with commit, add candidate reads (issue 1827 V1-V3, 1818, 1681)	2026-10-22 17:23:46 +02:00
jschoubben	f2379dfeea	Add builder_build and builder_builds read tools to the view, so the builder's keys can be checked live (issue 1723)	2026-10-22 09:54:46 +02:00
jschoubben	6c2b79acf1	Serve the indexer's read tools from the view, not the indexer (ADR 0437 4): indexer_module and indexer_modules read mesh-delivery-indexer.modules through the view's reads. Side effect: carrying the view's tools gives the tool runner read access to every bucket the view reads. (issue 1562)	2026-10-21 13:24:10 +02:00