gabriel / musehub public
docs musehub#113 task/investigate-silent-partial-clone #6 / 11
AI Agent gabriel · 16 days ago · Jul 1, 2026 · Diff

docs(musehub#113): full code trace — locate eager-vs-promised decision point and mpack.index job; resolve open questions 2/3; narrow to one remaining loose thread

sha256:6a01496f0414204e3954d5d77fd8b060817860b7478255c3a47fa4da0ea62700 sha
sha256:d4911a4331f42ef1e678e024fa74d5d230953732fd3f8c973af9b94c8d13d4ff parent
+11 ~3 symbols
sha256:0713ad993c6db5d2246702a343e0f858781ab1cc49ed8ce8d301e688ac9b1c03 snapshot
+11
symbols added
~3
symbols modified
0
dead code introduced
Semantic Changes 14 symbols
~ docs/issues/silent-partial-clone-promised-object.md .md 11 symbols added, 3 symbols modified
+ Code trace — where eager-vs-promised is actually decided section Code trace — where eager-vs-promised is actually decided L429–577
+ py) is generic and reactive, not a decision point section 1. ObjectState.PROMISED (muse/core/object_availability.py) is generic and reactive, not a decision point L434–453
+ code[python] variable variable code[python] L436–444
+ py:781-794) is client-push-only, confirmed not used server-side section 2. build_mpack's promisor-skip logic (muse/core/mpack.py:781-794) is client-push-only, confirmed not used server-side L453–476
+ code[python] variable variable code[python] L455–465
+ py) section 3. The real server-side gate — wire_fetch_mpack (musehub/services/musehub_wire_fetch.py) L476–510
+ code[python]@L480 variable variable code[python]@L480 L480–492
+ code[python]@L502 variable variable code[python]@L502 L502–505
+ py:1571) — objects are never stored standalone section 4. process_mpack_index_job (musehub/services/musehub_wire_push.py:1571) — objects are never stored standalone L510–524
+ py:913) — real inconsistency found, but confirmed inactive section 5. process_mpack_gc_job (musehub/services/musehub_wire_fetch.py:913) — real inconsistency found, but confirmed inactive L524–541
+ The one loose thread — why does feature-b's indexed oid fail all three retrieval strategies? section 6. The one loose thread — why does feature-b's indexed oid fail all three retrieval strategies? L541–577
~ Silent partial clone: required blob missing from working tree, clone exits 0, verify reports all_ok: true
~ Plan — reproduce at the most atomic level possible
~ What we don't know — open questions to close before any fix is attempted
Older docs(musehub#113): record atomic repro 4 — reproduced at minimal… sha256:d4911a4331f42ef1e678e024fa74d5d230953732fd3f8c973af9b94c8d13d4ff All commits Newer docs(musehub#113): ROOT CAUSE CONFIRMED — reproduced against loc… sha256:535dc3b5070c5179cdd6e782dbe5ddce10ae0446b833564d887eb68d2e7e9aef

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:6a01496f0414204e3954d5d77fd8b060817860b7478255c3a47fa4da0ea62700 --body "your comment"