docs
patch
fix/wire-push-external-parent-manifest
#1 / 4
docs: fix stale bare-hex claim in repair-object/repair-snapshot docstrings
Both docstrings claimed a bare 64-char hex ID was accepted (or accepted as an alternative to the prefixed form). Neither wire_repair_object nor wire_repair_snapshot normalizes the input -- they compare directly against blob_id()/compute_snapshot_id()'s output, which is always sha256:-prefixed per the ecosystem's Cryptographic Value Codec convention (never a bare hex string). A bare-hex snapshot_id silently fails with a hash-mismatch error that looks identical on both sides of the comparison, which is exactly what happened repairing musehub#134's corrupted snapshots on staging.
sha256:09bfcf29fa75b8c59d1c3bdba789cebc6ee19c2e3b7b238539ea08f78c7adfd4
sha
~2
symbols
sha256:db12a9a78feba8d8acbc0d4292748626037c6603b481fe05e8f2c7ed10f5f0fb
snapshot
~2
symbols modified
0
dead code introduced
Semantic Changes
2 symbols
Older
fix(musehub#134): reconstruct external delta-only parent instead of {}
sha256:281d7e2bfa6d4378354b0287c78e3bf1902581c486d072d3352c9d645ba81f63
All commits
Newer →
Latest on fix/wire-push-external-parent-manifest
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:09bfcf29fa75b8c59d1c3bdba789cebc6ee19c2e3b7b238539ea08f78c7adfd4 --body "your comment"
No comments yet. Be the first to start the discussion.