
The sandbox says what it refused
On Linux, the vx installed from npm reports a write its sandbox refused, with the grant to add, and blocks unix sockets again. A sandbox that reads none of its project offers the whole-project grant.
vx watch keeps hearing a directory that was removed and made again, as git stash and a branch switch do. A damaged cache file is named with its remedy, and distributed runs end tasks sooner.

vx watch could stop hearing a directory that was removed and then made
again. git stash -u, git stash pop and a branch switch all do that.
The project stayed unheard until the watch was restarted. This release fixes it, names a damaged cache file where a stack trace was, and lets distributed runs end tasks sooner.
In this release
The watcher drops a directory when it is removed. Its return could arrive as an event the runtime leaves out, so vx never watched it again.
Now a name that went is looked at once more, 50 ms later. Here
src/extra/ is stashed away, popped back, then edited:
$ vx watch build --all 1 task cached, nothing ranwatching 1 project · 1 taskchanged packages/lib src/extra/b.txt 1 task cached, nothing ranchanged packages/lib src/extra/b.txt 1 task cached, nothing ranchanged packages/lib src/extra/b.txt success miss +0ms 9ms 41% — 9B 0 local packages/lib#buildThe stash and the pop each restore a build the cache holds. The edit after them is heard and built.
See Running tasks.
With @vzn/vx-dte, a task another machine ran held its dependants until
its files were home and saved. They now start once the task ran, and the
save follows when the files land.
A task that declares no output ends on its worker’s word, with its log.
The footer’s ideal is now a floor: the run’s longest chain, with no
task waiting for room. No run can end before it. The planner’s figure
before the run reads as estimate.
See Distributed task execution.
store.db or cache index damaged in a page read after its open is refused by name, with the remedy; vx info says the same where it printed a stack..vx/cache was removed.inputs, itself behind a task with no inputs, is no longer saved under a key nothing can hit.exec.sandbox.weakerWhenNested now reaches the sandbox, so sandboxed tasks run in a container that refuses a fresh /proc mount.@vzn/vx-cache keeps the remote on after one read gets no answer, and asks once more; before, one silence failed a distributed run.bunx @vzn/vx-migrate pins the plugins it installs to the workspace’s installed vx.@vzn/vx is published once npm shows its platform packages, so an install minutes after a release gets its binary.vx upgrade