NousResearch/hermes-agent

Atomic checkpoint metadata writes to prevent corruption

Cluster 98832 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items address a bug where project metadata was not written atomically during checkpointing, risking silent data loss or corrupt JSON if a crash occurred mid-write. The proposed fix uses a temp-file-then-rename/replace approach to make writes atomic.

Open issues1

  • Issue#98832[P1] Checkpoint project metadata not written atomically — silent /rollback loss

Open PRs1

  • PR#98839fix(checkpoint): write project metadata atomically via temp+rename

1 PR closed without merging

From the close comments: duplicate 1

  • #99109 fix(checkpoint): write project metadata atomically via temp+replace to prevent corrupt JSON on crash · duplicate → #98839
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.67: 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

Subsystem
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.