NousResearch/hermes-agent
Windows atomic file replace sharing violation fixes
Cluster 57775 · agent. Data as of
Nothing open on GitHub. Fix merged in #84852 on 12 Aug 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #84852. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #84852. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests concern a bug on Windows where atomic file replacement operations lose written data when a sharing violation occurs due to concurrent readers. Multiple fix attempts address handling of ERROR_SHARING_VIOLATION in the atomic_replace utility.
Open issues0
Open PRs0
Fixes on record
-
#84852 fix(utils): recover Windows renames contended by an open handle
files:
tests/test_atomic_replace_symlinks.py,utils.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#57775Windows: atomic_replace drops writes on ERROR_SHARING_VIOLATION (concurrent reader of gateway_state.json et al.)
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
- Subsystem
- agent
- Merged PRs
- #84852
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 12 Aug 2026