{"repo":"NousResearch/hermes-agent","public_id":"120888","display_label":"Limit SQLite backup duration with wall-clock deadline","summary":"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.","subsystem":"hermes_cli","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":1,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":120888,"title":"Full backup can run indefinitely under concurrent writes despite BUSY/LOCKED timeout","url":null,"state":"open"},{"kind":"pr","number":120891,"title":"fix(backup): bound SQLite backup duration","url":null,"state":"open","close_reason":{"category":"partial_fix","implication":"needs_llm"},"merged":false},{"kind":"pr","number":121869,"title":"fix(backup): bound full SQLite snapshot with absolute wall-clock deadline","url":null,"state":"closed","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}