Cairn
NousResearch/hermes-agent

Fix memory update_fact duplicate content constraint crash

Cluster 43389 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These issues and pull requests address a bug where update_fact() crashes or errors when attempting to update memory content to a value that already exists, violating a UNIQUE constraint. The proposed fixes involve guarding against or gracefully rejecting such duplicate-content updates.

Open issues1

  • Issue#43389fix(memory): update_fact crashes on UNIQUE constraint when updating content to a duplicate

Open PRs2

  • PR#43399fix(memory): handle UNIQUE constraint in update_fact() (#43389)
  • PR#43404fix(memory): reject duplicate-content update instead of crashing

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #43401 fix(memory): guard update_fact against UNIQUE constraint on content · superseded by another PR → #41369
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.50: 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.

cluster/43389.json
cluster/43389.md