TraceResolve

General Resolution: [build] AssertionError [ERR_ASSERTION]: tick 2 must produce exactly one

[build] AssertionError [ERR_ASSERTION]: tick 2 must produce exactly one block
Immediate Remediation
bash
// File: test/solo-node.test.ts (patch)
/**
 * `handoff node --solo`: a block every 500 ms, driven by the injected clock.
 *
 * ## Why this is a clock-injected test
 *
 * The criterion is "a block every 500 ms". Asserting that against a real clock
 * would mean a test that sleeps for seconds and flakes under load. Instead the
 * node runs on a `VirtualClock` and the test advances it in exact 500 ms steps.
 * That is a *stronger* claim than a wall-clock test: it proves the cadence is
 * exactly the configured interval with no drift, which a wall-clock test cannot
 * show. The real `SystemClock` wiring is exercised separately by the CLI test in
 * `test/cli.test.ts`.
 *
 * ## What is real here
 *
 * Everything except time: real Ed25519 signatures, the real mempool, the real
 * lane ordering, the real state machine, and a real NDJSON log on disk. The
 * fixture is `soloFixture()`, which opens the node on the same devnet genesis
 * the CLI signs against — so a passing test says something about the CLI too.
 */
Root Cause Analysis

Compiler/Runtime incident captured during execution (patch_file). Verified recovery delta transitioned diagnostics to 0 errors.

Verification & Guardrails

  • [Verified RLVR Trajectory] · Compiler-Verified Loop in Rescriptum IDE · Health 100%
  • Verified Tool: patch_file
  • Exit Code: 0 (Verified)

Have a custom or uncategorized crash?

Run your trace through our in-memory client privacy sandbox for instant SRE remediation.

Open Diagnostic Studio