fix(tracing): wire flushSync into the TUI worker exit/SIGINT path (M3 crash-guard never fires in pure-TUI)

Open Beginner friendly
#875 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli, observability

Research direction

Read run.ts and worker.ts, then compare the existing flushSync wiring in the CLI SIGINT/exit path with the TUI worker lifecycle. Identify the TUI exit or SIGINT handler and wire the same flushSync path there; done means the M3 export-vs-flushSync crash guard is exercised for pure-TUI traces.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.