Skip to content

v1.5.0 — a store you forgot should stay forgotten

Choose a tag to compare

@dthorntonz dthorntonz released this 24 Aug 15:20
· 2 commits to main since this release

A number the disk-budget policy acts on was counting files nobody meant to keep, and there was no way to take one out — so the fix is a verb that removes a store from the count and, more to the point, remembers that you did.

Added

  • usage --forget <path> stops counting a store toward machine usage, and --unforget puts it back. Any store opened with --db joins the machine registry permanently, so backups and throwaway stores registered themselves and inflated the total — on a real machine it read 63.8 MB against a true 16.8 MB.

    The choice is remembered rather than merely applied. Every connect re-registers, so removing the entry alone is undone by the next incidental open. A forgotten path is recorded and consulted at registration, so it takes --unforget to reverse. The store file is never touched, and a path can be forgotten before it exists, so one that reappears stays excluded.

Fixed

  • A function-local from pathlib import Path in one branch of the CLI dispatcher made Path local to the whole function, so any use of it earlier in that function raised UnboundLocalError.

pip install "git+https://github.com/itdtllc/fornixdb@v1.5.0"

1132 tests + 1 skip. No store-format change; v14 schema unchanged.