Repository navigation
v1.116.0
Pre-release
Pre-release
Added
cctally doctor,cctally db statusand the dashboard's Doctor chip now say when a stats.db upgrade rebuild or auto-heal is running, has stalled, failed or died, or used more memory than its bound.
Changed
- The stats.db upgrade rebuild that runs after an update,
cctally db rebuildandcctally db rederiveuse far less memory and disk, and the upgrade rebuild finishes faster.
Fixed
- After a usage credit,
cctally statuslinerefuses an idle session's cached usage once it is proven stale, and five-hour views stop hiding genuine weekly values.cctally db rederiveaddsretract; stats.db rebuilds once after upgrading. - Under Python 3.11,
cctally quota --jsonno longer reports a mix-support radius that differs in its last digits from one run to the next. cctally quota --jsonreports the sameeligibilityFenceon Linux as on macOS; on Linux it could differ in its last digits.- A sync with nothing new to read no longer rewrites the compressed Codex rollout status in
cache.dbandconversations.db, so an idlecctally dashboardwrites less to disk. cctally cache-sync --rebuildrebuilds transcripts again on a filesystem without copy-on-write clones, such as ext4 on Linux, instead of failing every time.- On Python 3.11, the upgrade that moves transcripts out of
cache.dbnow shrinks the file as intended. If you already upgraded on Python 3.11, runcctally db vacuum --db cacheto reclaim the space.