mesh-delivery

novox/mesh-delivery

Fork 0

Files

T

History

jschoubben 726bbf1f1f

mesh/delivery merged: source.main moved to novox/mesh-delivery@2ac146078f47

Details

mesh/check being carried to 726bbf1f1ffa on 2ac146078f47 | from e753009fbc71

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)

The view remembered a reach value, a reached head and a motion event as written or said before the bus took them; a write refused at its start (no responders) was never made again while the derivation stayed the same, and mesh-delivery.show said mesh-delivery-view not running on shanks while node_haves said it running.

Quick fix: forget only the refused reach write. Thorough fix, chosen: every write and event the view makes after its lock (reach, reached head, delivered revision, motion) answers its error, and the model forgets what was refused, so the next change it takes in makes it again; one place, the writer of the state both mesh-delivery.show and knowledge-base.progress read.

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

cmd

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

files

Place the view's command as one file in /usr/local/bin, not the directory mesh-cli declares (issue 1134)

2026-10-19 00:09:54 +02:00

internal/view

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

go.mod

mesh-delivery-indexer and mesh-delivery-view pin mesh-sdk 3028c7e, the group's head after review round 2 (issue 1126)