zeekayandHanzo Dev ecb87b5eb5 zap: an error the wire has no word for must not read as success ...

ErrorUnspecified is the zero value and carries "the call succeeded" — a reply
holding it is read as a good answer and its fields are trusted. The only other
codes name a closed database and a missing key, so every other failure had
nowhere to go and was reported as the zero. A caller then took a zero-valued
block as a real one.

ErrorInternal gives those failures a word. Appending is safe in both
directions: errorFromZAP's default arm turns an unknown code into an error, so
a reader that predates this still sees a failure rather than a success.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-15 22:40:11 -07:00

..

atomic_test.go

zap: carry the cross-chain atomic seam across the plugin boundary

2026-08-06 14:08:52 -07:00

atomic.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00

doc.go

Add ZAP wire protocol transport for VM communication

2026-01-24 11:39:40 -08:00

LLM.md

docs(zap): canonical TCP port 9999 documented

2026-05-06 10:37:28 -07:00

sender.go

fix(zap): bound element counts before make() to stop unbounded-alloc DoS

2026-06-06 20:46:47 -07:00

transport_test.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00

transport.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00

vm_test.go

fix(zap): length-tolerant InitializeResponse decode (evolvable VM wire)

2026-07-16 12:31:15 -07:00

vm.go

zap: an error the wire has no word for must not read as success

2026-08-15 22:40:11 -07:00

warp.go

fix(zap): bound element counts before make() to stop unbounded-alloc DoS

2026-06-06 20:46:47 -07:00

wire_test.go

Add ZAP wire protocol transport for VM communication

2026-01-24 11:39:40 -08:00

wire.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00