jschoubben 704fc8d467 The forge bridge reads a merge's module directories only where their tree changed (issue 1126) ...

mesh-catalog's 140 module directories are 420 forge reads per merge, past the 30 s bound
of a handled event while the forge is busy: the merged message of #535 timed out on every
try, and #3fb7951 needed seven (issue 1458 met the same kind at 131). A tree hash names its
bytes, so what was read at a tree is kept in the new state inputs and in memory, and a
merge reads only the directories it changed.

2026-10-28 11:10:09 +01:00

..

cmd/mesh-delivery-forge-bridge

The forge bridge reads a merge's module directories only where their tree changed (issue 1126)

2026-10-28 11:10:09 +01:00

internal/bridge

The forge bridge reads a merge's module directories only where their tree changed (issue 1126)

2026-10-28 11:10:09 +01:00

go.mod

Move every delivery part's bus connection onto mesh-sdk's module helpers: credential, pinned dial, own-stream subjects, durable consumer, and refuse a hand-written one (issue 1242)

2026-10-27 20:40:49 +01:00

go.sum

Move every delivery part's bus connection onto mesh-sdk's module helpers: credential, pinned dial, own-stream subjects, durable consumer, and refuse a hand-written one (issue 1242)

2026-10-27 20:40:49 +01:00

manifest_test.go

The forge bridge reads a merge's module directories only where their tree changed (issue 1126)

2026-10-28 11:10:09 +01:00

module.json

The forge bridge reads a merge's module directories only where their tree changed (issue 1126)

2026-10-28 11:10:09 +01:00

reads-outside

Mark the packages whose tests read files outside their directory, found by the review (issue 1935)

2026-10-24 04:39:03 +02:00