Cairn
NousResearch/hermes-agent

User bus adoption timing in restart recovery

Cluster 107614 · 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 items concern a bug where aborted-restart recovery fails to normalize the user bus before systemd probes or spawning the recovery child, causing false exit codes and silently skipped user-scope units. The associated fixes address adopting the user bus at the correct point in the recovery sequence.

Open issues1

  • Issue#107614[Bug]: aborted-restart recovery never normalizes the user bus — false exit 1 and user-scope serve units silently skipped

Open PRs1

  • PR#107625fix(update): adopt the user bus before spawning the fresh restart recovery child

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #107623 fix(update): adopt the user bus before the recovery child's systemd probes (#107614) · superseded by another PR → #107625
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/107614.json
cluster/107614.md