novox/mesh-contracts
10
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
5cb77ce69fc24dc5d8c82a32ac47ee6c8a1cf410
mesh-contracts/go/clients/nodeengineclient/enginereads
T
History
jschoubben 04c6a1eead
mesh/delivery merged: source.main moved to novox/mesh-contracts@0e12819cc727
Details
mesh/delivery-group group fix/engine-reads-and-compositions merged: every member is merged
Details
mesh/check checking 04c6a1eead98 on 0e12819cc727 | novox/mesh-contracts#8 in group fix/engine-reads-and-compositions
enginereads: the event heard is kept in the node's statement (issue 1975 note 6) 
Builds: issue 1975 note 6 (the lead's review round 1; no design line). The engine 'not yet' half is dropped there.

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:00:33 +01:00
..
calls.go
C7: the node-engine seat's client keeps the wait of every caller's kept manifest-reads calls, ReadsCalls beside Keeper.Unanswered, its bound's end asking once whether the machine is heard (issue 1966, ADR 0668 §3, ADR 0634 §1, ADR 0596 §2; review round 3, findings 1 and 2)
2026-11-10 04:54:06 +01:00
enginereads_test.go
enginereads: the event heard is kept in the node's statement (issue 1975 note 6)
2026-11-12 11:00:33 +01:00
enginereads.go
enginereads: the event heard is kept in the node's statement (issue 1975 note 6)
2026-11-12 11:00:33 +01:00