docs: Wall 24 root cause confirmed — W24-P1 rapid TLS + W24-P2 H2 lifetime limit
W24-A0: CONN_ROTATION_INTERVAL=1 fails at batch 2 (no R2 PUTs, muse-wire-test 2000 files) W24-A2: CONN_ROTATION_INTERVAL=999 succeeds for 8 batches / 2MB (muse-wire-test) W24-A2b: CONN_ROTATION_INTERVAL=999 fails at batch 28/62 for muse repo (~10MB cumulative)
Two orthogonal CF limits identified: - W24-P1: Fresh TLS handshake fails if opened within ms of previous close - W24-P2: Long-lived H2 connection terminates at ~batch 28 (~10MB cumulative)
Next: W24-B0 — binary-search minimum inter-client sleep for CONN_ROTATION_INTERVAL=1
CONN_ROTATION_INTERVAL reverted to 1 (diagnostic state, not working).
sha256:8b32ee4217b0b83a000b5a49499cae9ca58dd203281fdf302c6a425b751d0502
sha
+10
~42
−4
symbols
sha256:d61054347109cdfdd0cf7fd7ad527bc3d4753b1179d55e4e2c5aa3cec00110b8
snapshot
+10
symbols added
~42
symbols modified
−4
symbols removed
0
dead code introduced
Semantic Changes
56 symbols
~
docs/protocol/musewire-performance.md
.md
10 symbols added, 4 symbols removed, 42 symbols modified
~
code@L40
−
Wall 24 — SSLV3_ALERT_BAD_RECORD_MAC on large repo push with no R2 PUTs
section Wall 24 — SSLV3_ALERT_BAD_RECORD_MAC on large repo push with no R2 PUTs L1422–1499
+
Wall 24 — Two orthogonal CF limits after Phase 14 (no R2 PUTs)
section Wall 24 — Two orthogonal CF limits after Phase 14 (no R2 PUTs) L1429–1545
~
Wall log
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:8b32ee4217b0b83a000b5a49499cae9ca58dd203281fdf302c6a425b751d0502 --body "your comment"
No comments yet. Be the first to start the discussion.