You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(tracing): wire flushSync into the TUI worker exit/SIGINT path (M3 crash-guard never fires in pure-TUI) #875
Found during v0.8.1 release review (CTO, P2). The M3 crash-guard added in #865 only runs when flushSync fires, which is wired in run.ts (CLI SIGINT/exit) but not in worker.ts. In pure-TUI sessions the M3 export-vs-flushSync path is never exercised. Not a regression (no worse than before #865); add a flushSync call in a TUI exit/SIGINT handler so the guard actually protects TUI traces.
Closing as fixed on main: The TUI worker now calls traceConsumer.flushSync() during shutdown, and the CLI invokes that shutdown before terminating the worker. Please reopen if you still see this on v0.12.9 or later.
Activity
anandgupta42 commentedon Nov 5, 2026
Closing as fixed on
main: The TUI worker now callstraceConsumer.flushSync()during shutdown, and the CLI invokes that shutdown before terminating the worker. Please reopen if you still see this on v0.12.9 or later.