Skip to content

0.1.14: end ended background jobs, refuse a second build in one copy, and count deleted tests

Latest

Choose a tag to compare

@tomw1808 tomw1808 released this 17 Nov 18:29
cded3b8

Acts on the second field report in #5: 0.1.13 on Linux, with four workers at once on a Rust workspace.

Update: /plugin marketplace update flash-agents, update the plugin, then run node install.mjs in the plugin folder. This release needs the install step: the build refusal lives in the guard, which only install.mjs copies into the profile. A clone: git pull, then node install.mjs.

Fixed

  • Ended background jobs leave current. A job leaves current when the Harness tells its worker the job finished, or when the process an earlier sample found is gone, whether or not the worker ever reads the job. A job whose process is not found no longer borrows another process (a sleep 55) as its child. It is called "may be stuck" only while the latest sample still finds its own process. 19 one-second edit scripts no longer show up as "running 20m0s".
  • Edit scripts are not "one command rerun". A command that carries its own program (a heredoc, python3 -c) is left out of the "ran N times … with no file changed" warning: each one is a new program, and the files it writes are not seen as changes.
  • A worker in another slot's copy is named. A command or path that reaches into a sibling copy (cd …/slots/12 && cargo test) gets a warning in status and in the result. The sandbox only confines writes, so it can't refuse that read. Workers are now told to stay in their own copy.

New

  • The guard refuses a second build in one copy. A cargo, go, gradle or swift build is refused (CONCURRENT_BUILD) while the same worker's own build of that tool still runs, background or not. The refusal tells the worker to wait with job_output or stop the first with job_kill. cargo fmt, go version and other workers' jobs are not affected. Set guard.refuseConcurrentBuilds: false in flash.config.json to turn it off.
  • Deleted tests and grown files beside the diffstat. change.tests ({ removed, added, byFile }) counts test definitions over the whole patch: Rust #[test], Python def test_…, Go func Test…, @Test, XCTest, xUnit attributes, and JS it(/test(. Two cases now produce a warning that names the files: a patch that removes more tests than it adds, and existing files that grew by 1,000 lines or more.
  • An idle stop names the last tool result, with its length and how long ago it reached the model, so a stalled model can be told apart from a result too large to read.
  • Delegate skill: ask the worker to list every test that fails compared with the base, by file, and say in the brief when to run the whole suite.

Verification

1036 tests pass across the three suites (1025 in 0.1.13). Every fix has a test that fails without it. The new tests feed in the Harness's completion notice as dsh-tool-jobs writes it; no live Harness run has delivered one to the server yet, so the process-tree check also covers a job whose notice never arrives. The live suite was not run for this release.