NousResearch/hermes-agent

sync_back tar leaks and socket failures

Cluster 114437. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #114787 on 18 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #114787. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114787. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #114787, then check it covers your case.

Read #114787 Pick up a Lab task

A bug where sync_back() creates multi-GB temporary tar files that are not cleaned up, partly because tar exits with an error when encountering live sockets. Multiple fixes address leak prevention, socket tolerance, and orphan tar reclamation.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#114787 fix(file-sync): sync-back tolerates live sockets, reclaims hard-kill tars by owner PID, cap overridable (#114437, salvage #114440)

merged to main

files: hermes_cli/config_defaults.py, tests/tools/test_file_sync_back.py, tests/tools/test_sync_back_backends.py, tests/tools/test_vercel_sandbox_environment.py, tools/environments/daytona.py, tools/environments/file_sync.py, tools/environments/modal.py, tools/environments/ssh.py, tools/environments/vercel_sandbox.py, website/docs/user-guide/configuration.md

2 PRs closed without merging

From the close comments: superseded by another PR 2

#114438 fix(env): stop sync_back leaking multi-GB tars and failing on live sockets · superseded by another PR → f29f6a0, #114787, #114437, #114440
#114440 fix(tools): stop socket-ignoring tars from failing sync-back and leaking GBs · superseded by another PR → 97a84e4, cdceca4, #114438, #114437, #114440

Closed issues · 1

Closed#114437[Bug]: sync_back() leaks multi-GB /tmp tars and can fill the disk (tar exits 2 on gateway.sock; 6h sweep window)

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.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

Merged PRs: #114787
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114437.json
cluster/114437.md