Skip to content

0.1.11: fail a run that ends on a tool call instead of a report, keep build caches across restarts, and watch for stuck commands

Choose a tag to compare

@tomw1808 tomw1808 released this 07 Nov 07:55
0a56954

Acts on two field reports in #5: a week of 0.1.10 on Linux and Windows 11, and the root cause of the Windows named-pipe failures.

Update: /plugin marketplace update flash-agents, update the plugin, then run node install.mjs in the plugin folder. A clone: git pull, then node install.mjs.

Fixed

  • A run that ends on a tool call is a failure, not a success. A call that ended "ok" with an empty final message, or with its next tool call written out as text (DSML or invoke markup at a line start), now ends as status: "error" with finalMessageProblem. The patch so far is kept. A job's state in flash_status is its result's status, so the two never disagree.
  • Three-way merges without a saved base. A file without one now merges from the base blob named in the patch's index line, read from your repository. Each file gets its own result (applied, merged, conflict, failed). If any file fails, nothing is written and the result lists the files that would apply. A patch that itself adds conflict markers gets a loud warning, on a dry run too.
  • Failure warnings are clearer. They name the command after nice, timeout and env prefixes, and group spellings of one command. They quote the last line of output and read exit codes above 128 as signals. A fail-before run that the brief asked for is reported as info.

New

  • Every finished job's whole report is stored on disk by job id (reportPath), read-only and discard jobs included. flash_result returns it after a restart, and flash_cancel returns the patch it salvaged from the copy.
  • Build caches survive restarts. cache: folders move into a per-root store at shutdown, or when the next server finds the old one dead (never while a process of the slot lives). New slots claim them by atomic rename. Stores are trimmed to the slot count and aged out. doctor lists slot, cache and store sizes, a call warns below 10 % or 5 GiB free, and clean --caches empties them.
  • A process-tree watcher checks once a minute while a tool call is open, using ps or Win32_Process. current[].child names the longest-running child. A tree with no CPU and no new process for five minutes is flagged.
  • Smaller additions:
    • label on flash_task and flash_batch, and readOnly: true;
    • overlaps with other unapplied patches;
    • a warning when source: "head" leaves out uncommitted files;
    • a bad state_base logs its reason before the server exits.
  • Worker instructions:
    • no devices or whole-disk searches;
    • report what was not done or not run;
    • run checks after the last edit;
    • no unverified "pre-existing";
    • keep encodings;
    • on Windows: $env: does not carry over, ninja and parallel MSBuild hang, and cargo has no network.

Verification

866 unit tests pass (770 in 0.1.10). An independent review of the merged change found nine more defects in the cache moves, the marker check, the markup check and the process watcher. All are fixed, each with a test. The live suite was not run for this release, because the flash models it drives were out of credits.