log --json: retract entries have sid=null and expose target only in cbcl #14
Loading…
Add table
Add a link
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?
Summary
In
log --json,retractentries carry"sid": nulland expose their target only inside the opaquecbclblob. Retracts are therefore not individually addressable, and any de-dup/fingerprint keyed onsidsilently collapses all retracts together.Repro
Computing
sha256oversorted(entry.sid)reported 62 distinct of 67 because the 6 retracts all hashed asnull.Expected
"retracts": "s-…") instead of only withincbcl.Impact
Blocks reliable order-independent journal fingerprinting — which is exactly what two machines need to confirm corpus convergence when peer sync is degraded.
Env
elephant v0.1.2 (HEAD
4d58f06), macOS. FLF two-agent Rootclaim run (6 retracts by the peer agent).