jschoubben 6bc16d74db Write and take in a merge that leaves no module.json, so a module-less repository's reach is not held for ever and a removed last module is dropped (issue 1126) ...

The forge bridge wrote no merged message for such a merge, so taken.<repo> never moved
and the view held 'the indexer has not yet taken in <head>' (hq #490-#492). The bridge
now writes it with no trees; the indexer drops every module of the repository on it,
after the same order check as any merged message. The view needed no change: with the
taken key moving it reaches the merge, which its new row proves.

Needs mesh-sdk fix/1126-no-module-reach (a merged message may carry no trees).

2026-11-03 16:45:06 +01:00

..

answers_test.go

Take the assigner's ask in the SDK's layout and name the asking in the view's answer, so a stale answer never fills a later asking (issue 1297 B9 and B10)

2026-10-23 15:22:32 +02:00

asks_test.go

An answer to an earlier asking no longer blocks the next asking: the teller and the view tell the asking by the answer's warrant id (review round 2, R2-1)

2026-10-20 01:35:26 +00:00

backlog_test.go

Show the backlog of build asks per language and kind: waiting, held by a node, and the oldest waiting ask's age (issue 1887 A8a)

2026-10-23 16:14:00 +02:00

backlog.go

Show the backlog of build asks per language and kind: waiting, held by a node, and the oldest waiting ask's age (issue 1887 A8a)

2026-10-23 16:14:00 +02:00

dial_test.go

Serve the rows on a read-only socket and web page, and print them with mesh-delivery-cli (issue 1134)

2026-10-18 19:31:50 +02:00

fingerprints_newform_test.go

Show a fingerprint of the new form against the builder's key of it, since the indexer no longer writes the old form and no build record names the new (issue 1851, I5)

2026-10-22 18:16:18 +02:00

fingerprints_test.go

View: read no build record and no composition of the controller's: fingerprints against the builder's done keys alone, a move's judgement from the node agent's have (issue 1955, ADR 0571 §1, §6)

2026-10-29 23:08:46 +01:00

history.go

Never let a merge move a module backwards, and make the forge messages and a module's history readable (issue 1126)

2026-10-28 14:48:13 +01:00

holds_test.go

List holds and let the operator release or keep one again from mesh-delivery-cli (issue 1906)

2026-10-25 15:09:40 +01:00

holds.go

List holds and let the operator release or keep one again from mesh-delivery-cli (issue 1906)

2026-10-25 15:09:40 +01:00

reach_test.go

Write and take in a merge that leaves no module.json, so a module-less repository's reach is not held for ever and a removed last module is dropped (issue 1126)

2026-11-03 16:45:06 +01:00

reach.go

The view writes a reach or says an event again when the bus refused it, so a refused write never leaves the reach state at an older have (issue 1126)

2026-10-28 16:11:52 +01:00

read.go

view_tiers: a source revision's tiers worked out from the module graph at each call, and per module what it waits on now, its build, each node's want and have and each provision it awaits, the nodes offline named away (ADR 0603 §6)

2026-11-03 16:45:06 +01:00

serve_test.go

Show what the watchman says: offline presence, stuck keys and unreadable values, in the view and its command (issue 1168)

2026-10-19 00:55:19 +02:00

serve.go

List holds and let the operator release or keep one again from mesh-delivery-cli (issue 1906)

2026-10-25 15:09:40 +01:00

status.go

View: answer status from the buckets it reads and derive motion with mesh-sdk's MotionOf, so status leaves the controller and the keeper judges a delivery as the view does (issue 1952 V1)

2026-10-29 21:52:42 +01:00

tiers.go

view_tiers: a source revision's tiers worked out from the module graph at each call, and per module what it waits on now, its build, each node's want and have and each provision it awaits, the nodes offline named away (ADR 0603 §6)

2026-11-03 16:45:06 +01:00

usage_test.go

View: build_usage reads each node's capacity as the integer mesh-config resolves for it, default 0, since no repository names a node (ADR 0567 §12, issue 1126)

2026-10-28 18:35:14 +01:00

usage.go

View: build_usage reads each node's capacity as the integer mesh-config resolves for it, default 0, since no repository names a node (ADR 0567 §12, issue 1126)

2026-10-28 18:35:14 +01:00

view_test.go

Read and write the seat mesh-placement's state as one key per module and node, converting each node's placement.<node> once at the holder's start (issue 774, research 072 row 37)

2026-10-31 09:32:32 +01:00

view.go

View: read no build record and no composition of the controller's: fingerprints against the builder's done keys alone, a move's judgement from the node agent's have (issue 1955, ADR 0571 §1, §6)

2026-10-29 23:08:46 +01:00

wants_test.go

View: read no build record and no composition of the controller's: fingerprints against the builder's done keys alone, a move's judgement from the node agent's have (issue 1955, ADR 0571 §1, §6)

2026-10-29 23:08:46 +01:00