Memory replace truncation and silent data loss fixes
Cluster 117952. Data as of
Nothing open on GitHub. Fix merged in #117988 on 21 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117988. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117988. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where a partial-entry memory replace operation silently overwrites or truncates the entire entry. The cluster covers the bug report and multiple related fix attempts addressing the behavior and its failure mode.
Open issues0
Open PRs0
Fixes on record
-
#117988 fix(memory): replace states and surfaces the whole-entry contract — no more silent truncation (#117952, salvage #109177)
files:
contributors/emails/[redacted:email],hermes_cli/write_approval_commands.py,tests/tools/test_memory_tool.py,tests/tools/test_write_approval.py,tools/memory_tool.py,tools/memory_tool_store.py,website/docs/user-guide/features/memory.md
2 PRs closed without merging
From the close comments: partial fix 1 · superseded by another PR 1
Closed issues · 1
- Closed#117952[Bug]: write-approval apply of a partial-entry memory replace truncates the whole entry — silent data loss
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.00means 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 LabAt a glance
- Merged PRs
- #117988
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 21 Sep 2026