Skip to content

fix(hermes): a session still in state.db-wal reaches recall, and a /branch's recall leaves out its source - #5142

Merged
vshulcz merged 1 commit into
hunt/harness-2026-10-17from
hh2/hermes-J
Oct 17, 2026
Merged

vshulcz merged 1 commit into
hunt/harness-2026-10-17from
hh2/hermes-J

Conversation

@vshulcz

@vshulcz vshulcz commented Oct 17, 2026

Copy link
Copy Markdown
Owner

The walk fingerprinted a SQLite store by the db file alone. Hermes writes go to state.db-wal until a checkpoint, so new sessions never got indexed. It now counts the -wal's size and mtime too, in fields of its own: the reader-sidecar fields would send a thin-titled DB session through the whole-session re-read. /branch sessions are read as forks of model_config._branched_from, and an unindexed branch is looked up by id in the sessions table so lineage leaves its source out.

Tests: TestAStoreThatWroteOnlyItsWALReadsAsChanged, TestAHermesBranchsRecallLeavesOutItsSource (both fail before), TestAHermesBranchIsAForkOfItsSource. Branch rows indexed before this pick up the fork kind when they are re-read or on deja index --rebuild; no index version bump.

Closes #5140, Closes #5141

@vshulcz vshulcz added the bug Something isn't working label Oct 17, 2026
@github-actions github-actions Bot added the windows Windows-specific label Oct 17, 2026
@vshulcz
vshulcz merged commit de53e6b into hunt/harness-2026-10-17 Oct 17, 2026
25 checks passed
@vshulcz
vshulcz deleted the hh2/hermes-J branch October 17, 2026 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working windows Windows-specific

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant