Skip to content

fix: only flush OoT LightEvent diagnostics when enabled - #9

Open
baromas wants to merge 1 commit into
MD5Visual:feat/oot-bootfrom
baromas:review/oot-light-event-logging-md5
Open

baromas wants to merge 1 commit into
MD5Visual:feat/oot-bootfrom
baromas:review/oot-light-event-logging-md5

Conversation

@baromas

@baromas baromas commented Nov 7, 2026

Copy link
Copy Markdown

The LightEvent wrappers already gate their log lines behind TOTK_WAIT_LOG. They still flush stderr after every wait and timed wait. Gate those two flushes as well. Guest calls, timeouts, and results use the same path with logging on or off.

The focused fixture passed in both modes on the MD5Visual base. This changes logging overhead only. The task-ring stall remains open.

Gate the remaining diagnostic flushes and verify guest calls, 64-bit timeouts and return values with logging on and off.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant