NousResearch/hermes-agent

Windows update relaunch exit-code and atexit handling

Cluster 115563. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

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

Read #116804 Pick up a Lab task

These items address a Windows-specific bug where an 'Already up to date' update path incorrectly exits with code 1 on a gateway relaunch verification failure, and an atexit callback re-raises the error. The work involves correcting exit behavior and disarming the atexit handler symmetrically.

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.

#116804 fix(update): Windows 'Already up to date' run warns on an unverified gateway relaunch instead of exiting 1 twice (#115563, salvage #115615)

merged to main

files: hermes_cli/update_cmd.py, hermes_cli/update_cmd_windows.py, tests/hermes_cli/test_windows_update_restart_reconciliation.py

1 PR closed without merging

From the close comments: merged via another change 1

#115615 fix(cli): symmetric Windows resume-failure handling + atexit disarm · merged via another change → 18f4b29, #116804, #115563, #115615

Closed issues · 1

Closed#115563[Bug]: Windows "Already up to date" update aborts (exit 1) on a relaunch-verification failure the pull path treats as non-fatal — and the atexit callback re-raises it

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

Merged PRs: #116804
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/115563.json
cluster/115563.md