Skip to content

0.1.13: count a command's process tree as activity, find the plugin's base folder from a shell, and start a copy from a diff file

Choose a tag to compare

@tomw1808 tomw1808 released this 14 Nov 19:16
· 1 commit to main since this release
a71f841

Acts on the field report in #5: 0.1.12 in daily use on Linux, a Rust workspace, up to ten workers at once.

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

  • clean and doctor find the plugin's base folder. The plugin setting reaches only the server, so the server now records the base it runs with in the repository's data directory. Run from a shell, both commands read that record when no flag, .flash-agents.local.json or FLASH_STATE_BASE names a base, and say which base they read and why. clean says when nothing of the repository was found there.
  • A worker inside its own long command is not stopped as idle. CPU used by a command's process tree (5 CPU seconds between samples), or a new process in it, counts as activity. An idle stop that still fires while the worker is inside its own command says so.
  • child counts its whole tree. treeCpuSeconds and treeProcesses sit beside the process's own CPU, and the progress line shows the tree's figure, so a cargo test whose test binaries do the work no longer reads as idle.
  • current names what the worker is waiting on first. A background job nobody waits on comes after it; one its worker has run three commands past is marked outlivedCommands and warned about.
  • "Failed N times" only for real loops. A failure counts as a repeat only when it fails the same way with no file changed in between. A heredoc or python3 -c with different code is a new attempt.

New

  • basePatchFile: start a call from a diff file inside the repository — say a branch in another git worktree. The diff becomes part of the copy's base, so the stored patch holds only the worker's own change, and overlaps no longer names every sibling.
  • Overlaps show where patches meet. Each overlap lists the meeting hunks (or disjointHunks: true, or hunksUnknown for a binary file), with sameBase. flash_apply lists them too, so a dry run tells you the order before anything is written.
  • limits.maxCacheBytes (FLASH_MAX_CACHE_BYTES, --max-cache-bytes; off by default): bounds a repository's build caches. Stored caches go first, then the cache of the slot idle longest; a busy slot is never trimmed. Sizes are read off the event loop.
  • New warnings:
    • one command rerun with four or more argument lists for twenty minutes or more, with no file changed between;
    • a build started beside a running background build of the same tool (cargo, npm, go, gradle and the like);
    • a load average above twice the hardware threads for at least a minute (not on Windows);
    • a brief that names an existing file outside the root, in the background call's first answer and in the result.
  • Workers are told to run one build at a time and to search with git grep or rg instead of grep -r … . over a build folder. The delegate skill says to name the helpers a brief should reuse, and to keep input files inside the repository.

Verification

1025 unit tests pass (1001 in 0.1.12); every fix has a test that fails without it. The tests no longer read the real volume's free space or use the real temp state base. The live suite was not run for this release.