feat: exhaustive logging for Wall 10 broken pipe diagnosis
- _frame_generator: log every frame (type, payload size, magic, total bytes) - client.stream: catch WriteError, log and re-raise as TransportError - log response headers/status on connect - log every rx chunk and frame type - docs: add Wall 10 entry, Phase 12, current open questions
sha256:67f40cf43342c88278d7eed321cd783a6e32dd4790d512366a02d3996e5fe85f
sha
+5
~12
−1
symbols
sha256:e9e830740eac0fbfc565a1fe4ea4fffb67ce6649ca695157f3667cd4e0f96133
snapshot
+5
symbols added
~12
symbols modified
−1
symbol removed
0
dead code introduced
Semantic Changes
18 symbols
−
Phase 11 — Legacy cleanup + Wall 9 fix ⬜ IN PROGRESS
section Phase 11 — Legacy cleanup + Wall 9 fix ⬜ IN PROGRESS L153–163
+
Phase 11 — Legacy cleanup + Wall 9 fix ✅ DONE (client side)
section Phase 11 — Legacy cleanup + Wall 9 fix ✅ DONE (client side) L153–163
+
Phase 12 — Wall 10 (broken pipe) 🔴 BLOCKED
section Phase 12 — Wall 10 (broken pipe) 🔴 BLOCKED L163–197
+
WriteError: [Errno 32] Broken pipe on streaming POST 🔴 ACTIVE
section Wall 10 — httpx.WriteError: [Errno 32] Broken pipe on streaming POST 🔴 ACTIVE L361–395
~
Wall log
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:67f40cf43342c88278d7eed321cd783a6e32dd4790d512366a02d3996e5fe85f --body "your comment"
No comments yet. Be the first to start the discussion.