Cairn
NousResearch/hermes-agent

Windows device-path blocklist path separator correction

Cluster 69373 · 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.

A bug caused the device/proc path read-guard to silently do nothing on Windows because backslashes were never matched against the POSIX-style blocklist. The correction normalizes path separators before comparison so the guard actually activates on Windows.

Open issues1

  • Issue#69373Windows: _is_blocked_device_path() is a silent no-op — normpath's backslashes never match the POSIX blocklist, and read_file genuinely hangs on /dev/zero via Git Bash's MSYS layer

Open PRs1

  • PR#69403fix(file-tools): make the device/proc read-guard fire on Windows

1 PR closed without merging

From the close comments: merged via another change 1

  • #69401 fix(file_tools): normalize path separator before device-path blocklist compare (#69373) · merged via another change
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/69373.json
cluster/69373.md