You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4bdef4e
Browse filesBrowse the repository at this point in the historyBrowse files
Keep knowledge snapshots that unfinished runs pinned
Strict and quality runs pin the knowledge snapshot active at reservation
(#213), and the design requires that a snapshot referenced by any unfinished
run is never deleted. Pruning kept only the newest ten plus the active one,
so a long queue could lose a pinned snapshot and fail those runs.
- activate.prune also keeps every snapshot that a run pinned
(<run>/knowledge.json) while that run is not terminal, or is an
interrupted reservation that never launched (it can be reclaimed and will
run with its original pin).
- Switching the active snapshot records when the previous one stopped being
active, and pruning never removes a snapshot deactivated less than an hour
ago. A reservation that resolved it just before the switch publishes its
pin within that window. The review runs live in other processes (and
possibly other hosts) that cannot share the service's activation lock, so
the coordination is this grace period.
- The run directories come from KB_RUN_ROOTS (os.pathsep-separated, for
several servers), else the runs' EFFECTIVE run_root (environment or the
.env files Settings reads).
- An autouse test fixture points KB_RUN_ROOTS at an empty directory, so tests
never read the real ~/.infermatrix-copilot/runs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments