shoney/writeonce
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
writeonce/docs/stories/language-runtime-database/07-logwatcher-proof.md
shoney.arickathil f8d3a8861c docs: reprioritise to log-watcher-executable only; update stories and plans 
Every remaining item is now traced to a measurement on the sample; anything the
sample does not exercise is deferred by name with the measurement that says so.

- new plan docs/plan/compiler/2026-08-14-logwatcher-executable.md — six tasks
  between "it runs" and "you can leave it running": the ownership pass learning
  stdlib return types (>1 MB leaked in 8s of `run` mode, one fs.read_all
  result), dropping a projected temporary (`for e in parse_dir(d).entries`
  leaks the shell per rescan), the runtime's own argv container (128 B every
  run), honouring the stop signal in blocking calls (a server in accept ignores
  SIGTERM), closing accepted connections (net.close exists, unused), and a soak
  that would have caught all of it. Opens with the measured starting point and
  closes with an explicit out-of-scope list
- story 7 (log-watcher proof): status banner separating the met compile-and-run
  half from the executable half, plus a new Given/When/Then — clean SIGTERM
  exit, zero leaks, flat RSS and descriptors across a soak
- story 5: grammar half landed, strictness half deliberately deferred
- story 6: landed for the surface the workload uses, with the two lifetime
  defects it exposed pointed at the new plan
- story 7b: recorded as off this workload's path, measured — the sample has no
  @gc class, 0 RC_INC/RC_DEC against 78 DROPs
- 00-status.md: NEXT PLAN is the executable list; story table and in-progress
  row point at the new plan; deferrals carry their evidence
- plan 8 (haxe-parity): banner now says on hold behind the executable plan, and
  its task states are corrected — Task 5 shipped, Tasks 6 and 7 are half done

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-14 22:16:14 +02:00

3.9 KiB
Raw Blame History

Iteration 7 — log-watcher proof workload

Format: fiberloom product/story-iteration-template. Part of Story — one language, one runtime, one database, one binary.

Goals

  • The language's driving workload runs for real: the Haxe log-watcher daemon (~1,200 lines) re-expressed file-for-file in .wo at docs/examples/log-watcher/, compiled by woc, detecting a silent death on a live file.
  • The README mapping table's "could not express" column is empty — the systems track's acceptance bar: nothing in a real daemon exceeded the language.

Status (2026-08-14): the compile-and-run half is met — the sample compiles with zero diagnostics, woc build produces a 106 KB standalone binary, and all three modes work (watch alerts, run schedules a cron.d entry, mcp answers JSON-RPC with all four tools returning isError:false). The remaining half is executable: under ASan both long-running modes leak (watch 128 B, run >1 MB in eight seconds), the MCP server never closes an accepted connection, and a server parked in accept ignores SIGTERM. That work is sequenced in plan/compiler/2026-08-14-logwatcher-executable.md and nothing else blocks this iteration.

Acceptance Criteria

  • What to achieve?
    • Given the eight-file .wo port (logtail, watcher, cron, probes, supervisor, mcp, tools, main),
    • when woc compiles the sample and the ported fixture groups run,
    • then compilation is clean and every fixture mirrors its named Haxe test case with matching behavior.
  • What to achieve?
    • Given the built sample running watch against a growing tempfile,
    • when the feed ends with an error line and the quiet period elapses,
    • then exactly one detection line appends to the JSONL sink — the original's measured behavior, reproduced.
  • What to achieve?
    • Given the README mapping table,
    • when the iteration closes,
    • then every row names its .hx sibling and deliberate divergences, and the could-not-express column is empty.
  • What to achieve? (added 2026-08-14 — compiling is not running)
    • Given any of the three modes started under a sanitizer build,
    • when it is signalled to stop after a soak,
    • then it exits cleanly on SIGTERM alone, reports zero leaks, and its resident size and descriptor count are flat across the soak.

Out Of Scope

  • The sqlite-backed minilog tools — expressible when iteration 9's SQL lands; recorded as scoped-out, not inexpressible.
  • New language or stdlib features: a gap found here is a defect report against iterations 5/6, and this iteration stops until it's resolved.

Info

  • The .wo files may be authored docs-first ahead of this iteration (spec 2026-08-07-logwatcher-sample-and-principles-design.md); this iteration is where they must actually compile and run.
  • The pure-core discipline (tail state machine, cron math, MCP handle socket-free and clock-injected) is preserved — the original's best design decision.

Proposed Solution

  • The authoring plan (docs/superpowers/plans/2026-08-01-log-watcher-sample.md) is spent: the .wo files exist and compile.
  • What remains is plan/compiler/2026-08-14-logwatcher-executable.md — six tasks, every one traced to a measurement on this sample: the ownership pass learning stdlib return types, dropping a projected temporary, the runtime's own argv container, honouring the stop signal in blocking calls, closing accepted connections, and a soak that would have caught all of it.
  • just log-watcher (scripts/log-watcher-accept.sh) is this iteration's gate: compile, watch alert, cron schedule, and three MCP checks today; the soak joins it in the last task.