PermissionError handling and file dedup cache fixes
NousResearch/hermes-agent · cluster 6214 · agent
Data as of
4 open items. Fix attempted, not merged.
The short answer
1open issue
3open PRs
14items grouped
- Known?
- Yes. 14 related items grouped here, 3 issues already closed.
- Fix event
- No fix has been merged to main. 7 PRs 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 3 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMultiple bugs and fixes around PermissionError when discovering context files in inaccessible directories, and read_file dedup/staleness logic incorrectly using host filesystem stats or returning stale results after writes.
Open issues1
- Issue#56380read_file dedup & staleness tracking stat the host filesystem, not the terminal environment
Open PRs3
7 PRs closed without merging
From the close comments: superseded by another PR 3 · merged via another change 2 · closed without comment 1 · other 1
- #6247 fix(prompt): ignore inaccessible context files · superseded by another PR
-
#6355 fix(prompt_builder): handle PermissionError during context file discovery · superseded by another PR →
#17100 - #8801 fix: catch PermissionError when walking parent dirs for context files · closed without comment
-
#13207 fix(tools): invalidate read_file dedup cache on write_file and patch · merged via another change →
a32b325 - #17100 fix(prompt_builder): handle PermissionError during context file discovery · merged via another change
Closed issues · 3
- Closed#6214[Bug]: `build_context_files_prompt()` raises PermissionError when TERMINAL_CWD points to an inaccessible directory (eg Daytona)
- Closed#8751Bug: PermissionError when walking parent directories for .git root
- Closed#13144[Bug]: read_file dedup cache not invalidated by write_file on same path — returns stale "not found" after successful write
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.12: 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
- Subsystem
- agent
- Closed issues
- 3
- Attempts
- 7 PRs closed without merging