NousResearch/hermes-agent

Update locking and race conditions in desktop pipeline

Cluster 123376 · hermes cli. Data as of 2026-10-27 11:58 UTC

1 open item. Fix merged in #127237 on 1 Oct 2026. Check it covers your case.

open issues

open PR

items grouped

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

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

Read #127237 Pick up a Lab task

These items address race conditions and locking gaps in the desktop update process, including issues where concurrent processes, interrupted updates, or stacked completions can corrupt build state or produce a persistent restart banner. The fixes focus on maintaining update locks correctly and resolving timing issues in the freshness pipeline.

Open issues0

No open issues.

Open PRs1

PR#127021fix(update): keep the update lock while its verified owner is alive

Fixes on record

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

#127237 fix(build,update): OS metadata, stamp-clock races and stacked completions break the desktop freshness pipeline

merged to main

files: apps/desktop/scripts/bundle-electron-main.mjs, hermes_cli/source_completion.py, scripts/build/README.md, scripts/build/desktop.mjs, scripts/build/freshness.mjs, scripts/build/frontend-common.mjs, tests-js/desktop-builder.test.mjs, tests-js/freshness-metadata.test.mjs, tests-js/frontend-common.test.mjs, tests-js/product-builders.test.mjs, tests/hermes_cli/test_source_completion_stamp.py, tests/hermes_cli/test_update_completion_process.py

Closed issues · 1

Closed#123376`hermes update` races with launchd-restarted gateways finishing the "interrupted" source update → mixed desktop build, permanent "Restart to finish update" banner

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
Merged PRs: #127237
Closed issues: 1
Attempts: 0 PRs closed without merging
Fix link checked: 1 Oct 2026

For your agent

The same facts, typed.

cluster/123376.json
cluster/123376.md