Cairn
NousResearch/hermes-agent

Kanban complete goal-mode judge_goal return value unpacking mismatch

Cluster 59762 · cron. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Members appear to concern the kanban completion gate in goal mode, where code unpacks the result of judge_goal() as three values while it is described as returning four. Some items are bug reports and others are fix proposals, and they describe the effects differently (a ValueError caught by a fail-open handler versus an orchestrator crash).

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: superseded by another PR 2 · duplicate 1

  • #59849 fix(tools): honor goal judge verdict in kanban_complete gate · duplicate → #57276, #58066
  • #61498 fix(tools): unpack all 4 judge_goal() return values in kanban complete gate · superseded by another PR → #57276, #61500, #61490
  • #61510 fix(kanban): unpack goal judge wait result · superseded by another PR → #57276
Closed issues · 2
  • Closed#59762kanban_complete` goal-mode judge gate never rejects: 3-target unpack of 4-tuple `judge_goal()` raises `ValueError`, caught by the fail-open handler
  • Closed#61490Bug: kanban_tools.py L605 — judge_goal 3-value unpack crashes orchestrator in --goal mode
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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
2
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/59762.json
cluster/59762.md