NousResearch/hermes-agent

Windows desktop update falsely reports failure after success

Cluster 109627 · apps/desktop. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
0 issues and 1 PR.

A bug on Windows causes successful desktop updates to report failure because a post-update PowerShell phase crashes before verification, writing default error values. The fixes aim to trap these exceptions and emit accurate receipts reflecting the true update outcome.

Open issues0

No open issues.

Open PRs1

  • PR#127290fix(desktop-update): a post-update crash yields a truthful receipt, never the opaque default (#109627)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #109646 fix(desktop-update): trap post-update exceptions and emit truthful receipts on Windows (#109627) · superseded by another PR
Closed issues · 1
  • Closed#109627[Bug]: [Windows] Desktop-triggered update reports FAILED (exit 1, 'update did not complete') after every *successful* update — post-update PowerShell phase dies before verify, finally writes script defaults
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
apps/desktop
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.