disk-load measures the items the node-engine keeps for its node, and composes nothing (ADR 0577)

It watches its node's keys of mesh-host_data instead of composing every module's items from
about 370 resolved keys per round, so a round no longer takes 30 to 45 minutes across the tunnel
and a manifest its mesh-sdk cannot judge no longer silences it. A changed key measures its module
at once; each round writes how far it got to the per-node state rounds, said by disk_round.
Pins mesh-sdk feat/data-items.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
This commit is contained in:
2026-11-01 00:15:14 +01:00
parent 444c2903af
commit b712123f2b
8 changed files with 307 additions and 64 deletions
@@ -5,6 +5,7 @@ import (
"encoding/json"
"os"
"strings"
"sync"
"testing"
"time"
@@ -12,15 +13,26 @@ import (
"git.novox.be/novox/mesh-sdk/go/health"
)
type memStore struct{ m map[string]json.RawMessage }
type memStore struct {
mu sync.Mutex
m map[string]json.RawMessage
}
func (s *memStore) Get(k string) (json.RawMessage, error) { return s.m[k], nil }
func (s *memStore) Get(k string) (json.RawMessage, error) {
s.mu.Lock()
defer s.mu.Unlock()
return s.m[k], nil
}
func (s *memStore) Put(k string, v any) error {
raw, _ := json.Marshal(v)
s.mu.Lock()
defer s.mu.Unlock()
s.m[k] = raw
return nil
}
func (s *memStore) Keys() ([]string, error) {
s.mu.Lock()
defer s.mu.Unlock()
var out []string
for k := range s.m {
out = append(out, k)