Skip to content

v0.4.0 — bounded execution and durable evidence

Choose a tag to compare

View all tags
@LBarimi LBarimi released this 04 Sep 17:40
v0.4.0
0dd3f08

FailTrace 0.4.0 adds execution controls and more efficient durable evidence for repeated debugging experiments.

  • Opt-in run --concurrency N, also available through Core and failtrace_run; the default remains sequential.
  • Bisect/minimize stop after their repeated-trial threshold is decided, preserving independent final minimization checks.
  • Incremental statistics and authoritative per-trial records avoid repeated growing metadata writes. loadRun reconstructs large compact summaries and recoverable records after interruption.
  • File-set minimization requests copy-on-write copies with an ordinary-copy fallback. Bundles preserve concurrency and replay the original full trial budget.
  • Reproducible benchmarks document measured improvements and remaining costs. Concurrency can change failure behavior through shared resources; early classification is not a full-budget frequency estimate.

Try the installed package:

npx --yes failtrace@0.4.0 demo

Requires Node.js 22.12+ and npm. CLI/Core/MCP, package installation and the real Prettier investigation are gated by CI on Windows, macOS and Linux with Node.js 22 and 24. The attached release.json records the exact source commit and CI run; SHA256SUMS identifies the reviewed archive.

Dedicated code-fix verification remains planned in this release. Performance scope · Changelog

Assets 5
Loading