René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Windows e2e: the daemon-crash step writes an internal-error line on stderr (fixed seed 3/10)","articleBody":"**Job:** https://github.com/TanStack/oracles/actions/runs/43661845394/job/132652674730 (Windows gap report end-to-end oracle, fixed seed 3/10, on #73 at `104376d`)\n\n**Test:** `fixed seed 20261105: an edit sequence through the daemon` (9.0 min on windows-latest)\n\n**Error:**\n```\noracle-gaps.report violated at checkpoint \"through the daemon at crash\" (law: greppable stream).\nDifference: through the daemon at crash: the run wrote a line on stderr that is not a line of the stream: This is a bug in oracle-gaps, not in your oracle. Its stack is in \u003cpackage>/out-daemon/error.log.\n```\n\n**What this is:** the daemon-crash step of the daemon history, on win32. The CLI writes an internal-error line on stderr, which the greppable-stream law rejects. The win32 daemon-crash path is not yet diagnosed. The stack is in `out-daemon/error.log` in the failing run's scratch directory, which the CI log does not include.\n\n**Not:** a finding about the oracle's history. Linux runs of the same history pass.\n\nFound while reviewing #73 (its body links this issue). Non-blocking: Windows end-to-end is non-blocking under C entry (c) until #79.\n","author":{"url":"https://github.com/KyleAMathews","@type":"Person","name":"KyleAMathews"},"datePublished":"2026-11-15T02:21:45Z","url":"https://github.com/TanStack/oracles/issues/86"}