Cairn
NousResearch/hermes-agent

Fix spurious promoted events when UPDATE hits zero rows

Cluster 77140 · cron. 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 address a bug in recompute_ready where promoted task_events are incorrectly fabricated even when an UPDATE statement affects no rows. The fix gates promotion bookkeeping on a rowcount check to prevent false events.

Open issues1

  • Issue#77140recompute_ready fabricates 'promoted' task_events when its UPDATE affects zero rows (missing rowcount check)

Open PRs1

  • PR#107340fix(kanban): gate recompute_ready promoted events on the UPDATE rowcount

1 PR closed without merging

From the close comments: partial fix 1

  • #77150 fix(kanban): skip promotion bookkeeping when UPDATE affects zero rows · partial fix → 7405e8c, #77140, #77150, #1, #15803, #14532, #6, #9, #374151, #4338
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
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/77140.json
cluster/77140.md