Cairn

Stale FTS rebuild and repair lock cleanup

NousResearch/hermes-agent · cluster 100108

Data as of

Nothing open on GitHub. Fix merged in #100525. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #100525. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests concern leaked or never-relinquished FTS rebuild and repair locks in state.db, including a reported case of the database bloating to 7.6GB, and several fixes aimed at reclaiming orphaned locks left by dead processes.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #100525 fix(state): break provably-orphaned repair/FTS-rebuild locks left by dead holders (#100108)

    merged to main

    files: hermes_state.py, hermes_state_common.py, tests/state/test_fts_rebuild_admission.py

3 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1 · superseded by another PR 1

  • #100130 fix(state): retry deferred FTS rebuilds instead of treating leftover lock files as holders · merged via another change → fd05029, c513861, dbb6acd, 894fc35, #101202
  • #100138 fix(state): reclaim leaked FTS rebuild locks when no live process holds the DB (#100108) · superseded by another PR → #100130, #100108
  • #103323 fix(state): reclaim leaked FTS rebuild locks when no live process holds the DB (#100108) · done elsewhere → #100525, #100108
Closed issues · 1
  • Closed#100108[Bug] state.db repeatedly bloated to 7.6GB, stale FTS rebuild locks left behind, repair locks never released
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#100525
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
1 Sep 2026

For your agent

The same facts, typed.

cluster/100108.json
cluster/100108.md