chore: yaad backup scheduler + intraprocess lock fix; wire hourly snapshots - #197
Merged
Conversation
- external/yaad -> fbc0466 (PRs #53-58: incremental HNSW, graph restore, backup rotation, backup scheduler, refcounted process lock) - go.mod pseudo-version bumped to match the gitlink (parity guard) - YaadBridge starts the hourly yaad backup scheduler once per process on the first ready bridge (~/.yaad/data/backups, keep 7, 30d)
Patel230
force-pushed
the
chore/yaad-backup-scheduler
branch
from
August 15, 2026 14:02
aa0dbe3 to
d8e7671
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps external/yaad to fbc0466 (PRs #53–58) and wires yaad's new backup scheduler into hawk's session startup.
yaad changes pulled in:
Store.ScheduleBackups— periodic VACUUM INTO snapshots with rotationNewStoreon the same DB was rejected by the flock merged in feat(storage): acquire cross-process lock on database open yaad#47; hawk opens multiple YaadBridges per session and would otherwise lose memory accesshawk wiring:
external/yaad→ fbc0466; go.mod pseudo-version aligned (release-parity check green)YaadBridge.EnsureBackups()starts the hourly snapshot loop (~/.yaad/data/backups, keep 7, 30d max age) — called only fromconfigureSessionHeavy(long-lived sessions, via cmd/options.go), never from bareNewYaadBridge()so diagnostics/tests don't leak schedulersYaadBridge.Close()stops the loop and releases the claim (with race-clean regression test)