Cairn

Kanban decomposed children runtime bounds propagation

NousResearch/hermes-agent · cluster 54089 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
4items grouped
Known?
Yes. 4 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
2 issues and 1 PR.

These issues and PRs concern a problem where auto-decomposed Kanban children do not inherit or enforce runtime and retry limits from their parent. The work involves propagating max_runtime_seconds and related bounds to decomposed children.

Open issues2

  • Issue#54089Decomposed Kanban children lose runtime bounds
  • Issue#63209Kanban: enforce native runtime/retry floors on auto-decomposed children

Open PRs1

  • PR#54104fix(kanban): propagate max_runtime_seconds to decomposed children (#54089)

1 PR closed without merging

From the close comments: other 1

  • #66405 fix(kanban): bound decomposed child runtimes · other → #54104, #66404
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.39: 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/54089.json
cluster/54089.md