Cairn
NousResearch/hermes-agent

read_file dedup cache: add content hashing beyond mtime

Cluster 53812 · 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 concern the read_file deduplication cache, which an issue describes as relying on mtime only and so potentially serving stale content after sub-second edits. Two pull requests propose hashing file content, in addition to mtime, for dedup cache entries.

Open issues1

  • Issue#53812read_file dedup uses mtime only — stale cache on sub-second edits

Open PRs1

  • PR#53816fix(tools): verify content hash alongside mtime in read_file dedup (#53812)

1 PR closed without merging

From the close comments: duplicate 1

  • #54281 fix(files): hash read dedup cache entries · duplicate → #53816, #53812
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.

cluster/53812.json
cluster/53812.md