Cairn
NousResearch/hermes-agent

Migration symlink same-file error handling

Cluster 24943 · hermes cli. 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 members address a failure in the claw migrate command when source workspaces contain symlinks that cause source and destination to resolve to the same file. The work involves detecting and skipping the copy operation in that scenario.

Open issues1

  • Issue#24943[claw migrate] Migration fails with "are the same file" when source workspace contains symlinks

Open PRs1

  • PR#24956fix(migration): handle symlinks and SameFileError in claw migrate workspace copy

1 PR closed without merging

From the close comments: other 1

  • #124423 fix(claw-migrate): skip copy_file when source and destination resolve to the same file (#24943) · other → 832d0bf, #24943
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/24943.json
cluster/24943.md