erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs(issues): close #351 with the verified root cause — deterministic Debug.Assert translation, not a flake (fixed in c6bc2bf7)

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-09 20:01:04 +02:00
parent c6bc2bf7eb
commit 852cdda784
1 changed files with 19 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/ISSUES.md
View file

@ -117,11 +117,25 @@ session; the live gate covered the behavior.
## #351 — LandblockBuildOriginTests.FarLoad_StripsEnvCellsAndPhysics flake (Debug, load-sensitive) ## #351 — LandblockBuildOriginTests.FarLoad_StripsEnvCellsAndPhysics flake (Debug, load-sensitive)
**Status:** OPEN (filed 2026-08-08). Seen three times today in Debug runs **Status:** CLOSED 2026-08-09 (`c6bc2bf7`). NOT a flake and NOT timing —
under parallel-agent load (5.4 implementer, Slice 6 corrections, dropdown the "load-sensitive" framing was wrong: it failed deterministically on
polish), each time proven pre-existing by re-running against the pristine EVERY Debug `dotnet test` run since the test landed (`090b0354`
base commit; never reproduces in clean-room Release. An async streaming introduced the test and the tripwire in the same commit; the
timing assumption most likely; deflake when it next blocks a verdict. parallel-agent-load correlation was just that Debug runs are rare — the
gate config is Release). Mechanism: the test feeds a far-tier factory
returning Near payload on purpose to prove the strip safety net, but
`LandblockStreamer.HandleJob` is documented "fail loud in Debug builds
and strip in Release" — its `Debug.Assert` fires on exactly that input,
the VSTest host translates the assert into a thrown
`DebugAssertException` (its message says so verbatim) instead of killing
the testhost, and the worker catch folds it into a `Failed` completion,
so `Assert.IsType<Loaded>` fails. Release compiles the assert out
(`[Conditional("DEBUG")]`) and strips — hence "never reproduces in
clean-room Release". Fix: the test now pins BOTH halves of the
config-divergent contract via `#if DEBUG` (Debug expects the loud
`Failed` carrying the assert text; Release keeps the strip assertions).
Production code unchanged; LandblockBuildOriginTests 11/11 in both
configs.
## #350 — Render-shadow ledger overflow after 2h42m: lifetime int counters in a never-reset accumulator ## #350 — Render-shadow ledger overflow after 2h42m: lifetime int counters in a never-reset accumulator