summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-node/src/meshbay_node
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-08-24 23:34:57 +0200
committerChristophe Besson <cbesson@gmail.com>2026-08-24 23:34:57 +0200
commitaeeaf0d537a1942010caf222b72333841b80b7f8 (patch)
treec1db2dab14a56e68edcf73de146cb52c1159fa1a /packages/meshbay-node/src/meshbay_node
parent1e6abbb8db76cdabd53b85d938ee0e76486f5ae4 (diff)
downloadmeshbay-aeeaf0d537a1942010caf222b72333841b80b7f8.tar.gz
test(node): a real signed audio_root save through the full challenge path
Every existing audio_root test either called ops.set_audio_root directly or mocked out _issue_admin_challenge — none of them exercised real signature verification, _do_admin_response, or the shared groups_ctx/ roster wiring _run_op depends on. Worth ruling out a break somewhere in that real path specifically: a report described a save that looked like it worked (the Music tab showed content right after) not surviving a reload. Drives the real _do_audio_root -> admin_challenge -> sign -> _do_admin_response -> _admin_exec_audio_root path with a genuine Ed25519 operator key, then opens a *separate* Roster instance against the same db file — the direct question a "worked, then reverted" report raises: does the value actually land durably, in a form any later connection reads back correctly. It does; this passes. The one thing missing from the session fixture to get this far was peer-registry self-registration (a real session adds itself on handshake completion — without it, the final ack has nowhere to go, including back to the requester).
Diffstat (limited to 'packages/meshbay-node/src/meshbay_node')
0 files changed, 0 insertions, 0 deletions