fix: send snapshot manifest under 'manifest' key not 'delta_upsert'
_snap_row_to_wire was sending manifest_blob as delta_upsert. The client applies delta_upsert on top of the parent snapshot — so deleted files linger, the reconstructed manifest differs, and hash_snapshot() returns a different ID than the stored snapshot_id.
Fix: use the 'manifest' key. The client treats it as the full manifest directly (no delta reconstruction), then hashes it to verify. Since snapshot_id = hash_snapshot(full_manifest), the check passes.
sha256:52b29c48bd61a50edb216d2dfc4f71d30ec2e0ab37326b3ab970826d5c9c0145
sha
~1
symbols
sha256:840e94b7c1927cc3b6fe13717b9565cfcd20709b322b109b9392603bb80b220e
snapshot
~1
symbol modified
0
dead code introduced
Semantic Changes
1 symbol
Older
diag: add per-stage FETCH-DIAG logging to blob extraction path
sha256:e1171ab8958a8dc1f3a25fce5b7eedda123042373bc977a377c358ea429ef43e
All commits
Newer
fix: reconstruct manifest for snapshots with null manifest_blob
sha256:3f188050991b4e062a2dc0f2f99ee17cb85b7723dbeaedf5f766180582110d7b
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:52b29c48bd61a50edb216d2dfc4f71d30ec2e0ab37326b3ab970826d5c9c0145 --body "your comment"
No comments yet. Be the first to start the discussion.