# NousResearch/hermes-agent · Limit SQLite backup duration with wall-clock deadline

## Open now

- 1 issue, 1 PR open on GitHub.
- #120888: Full backup can run indefinitely under concurrent writes despite BUSY/LOCKED timeout
- PR #120891: fix(backup): bound SQLite backup duration

These items address a bug where a full SQLite backup could run indefinitely when concurrent writes cause repeated BUSY or LOCKED conditions. The proposed fixes introduce an absolute wall-clock deadline to bound the total backup duration.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

- #120888: Full backup can run indefinitely under concurrent writes despite BUSY/LOCKED timeout

## Prior & competing PRs

- **#120891: fix(backup): bound SQLite backup duration**. open
  - maintainer direction: category `partial_fix`; implication `needs_llm`
  - files: `hermes_cli/backup_sqlite.py`, `tests/hermes_cli/test_backup.py`
- **#121869: fix(backup): bound full SQLite snapshot with absolute wall-clock deadline**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`