fix(tracing): sweep .tmp.* trace files even when maxFiles is 0 (unlimited)

Open Beginner friendly
#874 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
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
observability

Research direction

Start at the FileExporter entry point and inspect how pruneOldTraces is gated by maxFiles. Ensure the .tmp.* sweep also runs when maxFiles is 0, then verify that unlimited mode removes leftover temporary trace files from the user-private data directory.

Written by the indexing model from the issue text.

Description

Found during v0.8.1 release review (Chaos Gremlin, P3). Pre-existing.

FileExporter only sweeps leftover .tmp.* snapshot files via pruneOldTraces when maxFiles > 0 (default 100, so the common path is fine). With maxFiles: 0 ('unlimited'), repeated crashes can slowly accumulate .tmp.* files under the user-private data dir. Run the tmp sweep unconditionally, independent of maxFiles.

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.