The lease write stops the controller on its placed node and reads the operator's answer from the right bucket (issue 774) #135

Merged

mesh-tools merged 2 commits from fix/774-lease-write-node into main 2026-11-02 08:52:48 +00:00

Conversation 1 Commits 2 Files Changed 6

+120 -21

2 Commits

Author	SHA1	Message	Date
jschoubben	8f87dbe94d	mesh-delivery-teller: read asks from the router's bucket the grant names ... The teller read the router's record from KV_asks, a bucket no composed grant names, so every read was denied and its operator answers could not be read back. It now reads messenger_asks, as mesh-grants does. The integration bed grants the real subject and reads a record on the teller's credential, so it no longer agrees with the mistake. (issue 774) Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 09:44:26 +01:00
jschoubben	7cee3842b8	mesh-grants: stop the controller on its placed node and read asks from the router's bucket ... The lease write addressed node-service-manager at the lease holder's host, a hostname no node carries ("novox-be" on novox), so the operator's yes timed out at its first step and failed without a log line. The node now comes from placement (exactly one node placing mesh-controller, else refused by name), a failed act is logged beside its condition, and the asks record is read from messenger_asks, the bucket the composed grant names, instead of asks, which no grant allows. The fixtures give the lease a host unlike the node, so the tests no longer agree with the mistake. (issue 774) Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 09:42:19 +01:00