Cairn

Wrong PID exported in desktop update hand-off

NousResearch/hermes-agent · cluster 134268 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #134551. Check it covers your case.

The short answer

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

A bug causes desktop-initiated updates to export an incorrect PID as HERMES_UPDATE_HANDOFF_PID, causing them to block themselves with exit 2. The members cover the bug report and several fix attempts to export the marker's actual owner PID.

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.

  • #134551 fix: Desktop updates on macOS no longer refuse their own update lock after a relaunch (salvage #134269)

    merged to main

    files: contributors/emails/[redacted:email], scripts/desktop-update/posix.sh, tests/scripts/desktop_update/test_posix_handoff_pid_export.py

4 PRs closed without merging

From the close comments: done elsewhere 3 · merged via another change 1

  • #134269 fix(install): name the marker owner as the Desktop hand-off pid · merged via another change → 6660547, #134551
  • #134597 fix(update): export the marker's real owner as HERMES_UPDATE_HANDOFF_PID · done elsewhere → 6660547, #134551, #134269, #134875
  • #134875 fix(install): export the marker's owner as HERMES_UPDATE_HANDOFF_PID (+ behavioural test) · done elsewhere → 6660547, #134551, #134269, #134268
  • #135823 fix(update): export the custodian pid as HERMES_UPDATE_HANDOFF_PID · done elsewhere → 6660547, #134551, #134269
Closed issues · 1
  • Closed#134268[Bug]: Desktop hand-off exports the wrong pid as HERMES_UPDATE_HANDOFF_PID — every desktop-initiated update self-blocks with exit 2
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.33: 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
apps/desktop
Merged PRs
#134551
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
10 Oct 2026

For your agent

The same facts, typed.

cluster/134268.json
cluster/134268.md