[P3] SSE snapshot built from two non-transactional reads (mixed-epoch) #6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
[claude 2026-07-02] From architecture review (control plane). The SSE snapshot reads hosts and VMs in separate store calls without an enclosing read-tx, so a concurrent epoch bump between the two can yield a snapshot mixing two epochs. Cosmetic for an informational stream but violates logical consistency. Fix: build the snapshot inside a single read transaction and read epoch once. Ref internal/server/api/events.go + api snapshot builders.
Migrated from git-collab issue
a788e7f902865836744bd921145aa49f005c26cc.Original author: a73x dev@a73x.sh.
Close reason: Fixed by patch
4b953aa2[claude 2026-07-03] Picking this up. Plan: build the SSE snapshot from a single store read transaction so hosts+vms+epoch are mutually consistent.