novox/mesh-controller
18
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Pin the group's mesh-sdk ef1ec1c9 and capture its conformance files there, so the sweep builds on kvlimit and the named readers (issue 774)

Browse Source 
The sweep's controller changes use mesh-sdk's go/kvlimit and the ReadsAnnouncedBy that grants named
readers. At ef1ec1c9 mesh-config is a named reader of the controller's lease (its take-over reads it,
ADR 0561 §3), so the read test now expects it granted and a module not named refused. The captured SDK
(testdata/beside, conformance/events) is taken again at the pinned commit, as CAPTURED says; its file
is unchanged.
This commit is contained in:
jschoubben
2026-10-30 18:27:54 +01:00
parent 8c3d372322
commit 77c54445dc
4 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testdata/beside/CAPTURED
Vendored
+1 -1
View File
@@ -9,7 +9,7 @@ a second place to clean besides the catalogue itself.
mesh-catalog f3a57dcc56fb6c198095cafd11d0decff9f720c4 modules/*/module.json, modules/*/files, modules/*/templates, predefined.json
mesh-host 9d9e3a46c4f5943cfffb413d962ce48b75e2fd39 examples/foundation-first-node.lock
mesh-sdk 2da0de75c3f0087cff9c2f5ef789ca6dc3c59045 conformance/events/module-event.json
mesh-sdk ef1ec1c93544f0fc12b2dca608167bf2af11a846 conformance/events/module-event.json
To move them, from this repository's root, with the two repositories checked out beside it: