debugging-computerd-fuse
Debugging computerd against real FUSE
This skill captures the recipe for isolating bugs in computerd that only
fire when the kernel-FUSE backend is the one wired up. Most unit
tests run against SQLiteTestStorage and an in-process VFS or the
userspace FUSE_MOUNT=shim polling driver — neither exercises the
kernel-FUSE callback path. Several production-only bugs (write
buffer never spilled to the VFS, spawn(cwd=/mount) deadlocks)
have shipped to next and not been caught by the regular suites
because the harness is hard to drive end-to-end from a dev box.
The workflow here bypasses workerd, wrangler, and the
vitest-pool-workers harness. It boots the computerd SEA binary in a real
docker container with /dev/fuse and SYS_ADMIN, and drives its
capnweb endpoints from a plain Node script.