mirror of
https://github.com/d4rken-org/capod.git
synced 2026-09-14 18:26:11 -04:00
darken
2ba90e1d18
The flag was only written from committed recorder module state, which publishes after the recording header has been read. That read is bounded at 5s, so for up to five seconds the file logger is live while the flag still says false, and diagnostics keyed off it are missing from exactly the window a reporter uses to reproduce a screen-off issue. The module-state writer stays: it covers a resumed session and any path that reaches isRecording=false without going through Recorder.stop(). A rolled-back start self-corrects, because the rollback stops the recorder before publishing the failure. BaseTest resets the flag per test instance because it is JVM-global. It goes into init rather than the companion teardown, which uses JUnit 5's @AfterAll and never fires under the JUnit 4 Robolectric runner.