diag: add per-stage FETCH-DIAG logging to blob extraction path
Instrument every stage of the blob extraction pipeline so a single muse clone run reveals exactly where objects are lost: stage=A: content_cache hits vs misses stage=B: mpack_index lookup — oid_to_mpack count, no_mpack_oids, distribution stage=C: _extract_from_mpack — raw bytes, blob count in payload, found/missed stage=D: legacy per-object S3 fallback hits vs misses stage=E: final blob_pairs tally with unresolved sample
sha256:e1171ab8958a8dc1f3a25fce5b7eedda123042373bc977a377c358ea429ef43e
sha
~1
symbols
sha256:96cb50b2961079edd9d12c0822a8d5b5653e111da37a79044536f48e652ae696
snapshot
~1
symbol modified
0
dead code introduced
Semantic Changes
1 symbol
Older
refactor: remove dual fetch paths in _walk_commit_delta and callers
sha256:9dbd6015bfeb02e1832f9bdbe80ed58ee9138566f0f317c5557bbd571d6946ca
All commits
Newer
fix: send snapshot manifest under 'manifest' key not 'delta_upsert'
sha256:52b29c48bd61a50edb216d2dfc4f71d30ec2e0ab37326b3ab970826d5c9c0145
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:e1171ab8958a8dc1f3a25fce5b7eedda123042373bc977a377c358ea429ef43e --body "your comment"
No comments yet. Be the first to start the discussion.