docs(buglog): bug-1683 recurred during controller-peers-env-fallback task 4.1

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-03 07:31:38 +00:00
parent 6eab344c6e
commit e61a9acc65
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
2 changed files with 10 additions and 10 deletions

View file

@ -9658,14 +9658,14 @@
},
{
"id": "bug-1683",
"status": "fixed",
"status_updated": "2026-09-24",
"status_note": "",
"status": "open",
"status_updated": "2026-10-03",
"status_note": "2026-10-03, controller-peers-env-fallback task 4.1: xce-build.sh xceadmin --incremental run 1 failed test_wire.py::test_send_frame_writes_exact_known_good_byte_sequence (header captured, xce! payload missing); run 2 immediately after passed (314 passed). Diff under test touched only discovery.py/errors.py/test_discovery.py, so unrelated.",
"component": "xceadmin",
"severity": "unknown",
"timestamp": "2026-08-25T00:05:00Z",
"last_seen": "2026-09-19T09:00:00Z",
"occurrences": 2,
"last_seen": "2026-10-03T07:27:36Z",
"occurrences": 3,
"error_message": "xceadmin pytest failure: test_send_frame_writes_exact_known_good_byte_sequence…\n\nxceadmin pytest failure: test_send_frame_writes_exact_known_good_byte_sequence (src/xceadmin/tests/test_wire.py:200). Test sends a 4-byte payload b'xce!' via wire.send_frame() over a real TLS socket to a raw capture handler that reads exactly 12 bytes (8-byte length header + 4-byte payload) directly off the wire, bypassing this module's own recv_frame() decoder. Expected the captured bytes to be struct.pack('=Q', 4) + b'xce!' (header correctly encodes length=4, followed by the literal payload bytes). Actual captured bytes: the 8-byte header is correct (b'\\x04\\x00\\x00\\x00\\x00\\x00\\x00\\x00', i.e. length=4 little-endian native uint64_t), but the trailing 4 bytes are all zero (b'\\x00\\x00\\x00\\x00') instead of b'xce!' -- the real payload bytes never reached the wire. 1 failed, 266 passed, 3 skipped -- isolated to this one test.",
"file": "src/xceadmin/src/xcecommon/wire.py",
"root_cause": "UNRESOLVED -- not reproducible. send_frame() (wire.py:102-113) is two sequential sock.sendall() calls (header, then payload) -- nothing in it, or in the test's _TlsEchoServer/_capture_handler harness (test_wire.py), or conftest.py's session-scoped tls_certs fixture, could zero out payload bytes; all reviewed and found correct. Confirmed only bare pytest 8.4.2 is installed (no pytest-xdist, no pytest-randomly, no addopts) -- test order is deterministic, ruling out parallel-worker/reordering interference.\n\n45+ reproduction attempts (2026-08-25), zero failures: isolated run x5, full test_wire.py x3, full 270-test suite x3 (ad-hoc PYTHONPATH), full meson-driven build+test pipeline (xce-build.sh xceadmin, the project's real test-running convention) x1 clean (267 passed, 3 skipped), isolated via the meson-built venv x15, full suite via meson-built venv x5, full suite under artificial CPU stress (20x `yes` spinners, load 11+) x5, 8-way concurrent parallel execution of the exact test x8 -- all clean. TCP/TLS cannot spontaneously zero application bytes mid-stream, so a genuine code defect producing this exact symptom (correct 8-byte header, real zeroed 4-byte payload) should be deterministically reproducible, and it isn't.",

View file

@ -1,13 +1,13 @@
---
id: "bug-1683"
status: "fixed"
status_updated: "2026-09-24"
status_note: ""
status: "open"
status_updated: "2026-10-03"
status_note: "2026-10-03, controller-peers-env-fallback task 4.1: xce-build.sh xceadmin --incremental run 1 failed test_wire.py::test_send_frame_writes_exact_known_good_byte_sequence (header captured, xce! payload missing); run 2 immediately after passed (314 passed). Diff under test touched only discovery.py/errors.py/test_discovery.py, so unrelated."
component: "xceadmin"
severity: "unknown"
timestamp: "2026-08-25T00:05:00Z"
last_seen: "2026-09-19T09:00:00Z"
occurrences: 2
last_seen: "2026-10-03T07:27:36Z"
occurrences: 3
files: ["src/xceadmin/src/xcecommon/wire.py"]
tags: ["xceadmin", "xcecommon", "wire-protocol", "python", "framing", "test-failure", "unreproducible"]
related: ["bug-1604"]