Repository navigation
v21.0.1
·
2 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
A patch release. The brain format (version: 8), bf.yaml, the reply schemas, the queue format and the search cache are unchanged; no upgrade step is needed, except to recover a queue that a device renumbering already stranded (below).
Fixed
- A new device number no longer starts an empty assistant queue. BF names a brain's queue and program-state folders by its device and inode numbers, and btrfs can number a device anew at boot: the queue then looked empty, stranding unresolved work, and window sensors restarted from
lookback. When the folder for the brain's current identity is missing, BF now renames the folder with the same inode whose queue is bound to the brain's path, together with its program state; a brain without a queue still restarts its window sensors fromlookback. Several matching folders, or one that cannot be read, such as after an interrupted write, make assistant commands fail withseveral assistant queues in the state folder runtime/ are bound to this brain (…)orassistant queue in the state folder runtime/ (NAMES) may belong to this brain but cannot be readinstead of choosing; collection and watch keep running (move or rename a brain). - Recovering an already stranded queue (manual). A brain that already ran after a renumbering has a new, possibly empty folder, which this release keeps. To recover the old queue: stop
bf watch, check thatbf queueshows no work you need, moveruntime/NEW(named bystat -L -c %d-%i BRAIN, orstat -L -f %d-%i BRAINon macOS) out of the state folder, rename the oldruntime/OLD-INODEfolder toNEW(andprograms/OLD-INODElikewise), then runbf queue.