Kanban diagnostics severity filter threshold fix
NousResearch/hermes-agent · cluster 26379
Data as of
Nothing open on GitHub. Fix merged in #27292. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #27292. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple issues and PRs addressing a bug where the kanban diagnostics --severity flag performed exact matching instead of the documented 'at or above' threshold behavior. Includes one unrelated batch PR grouping miscellaneous contributions.
Open issues0
Open PRs0
Fixes on record
-
#27292 Batch salvage group 2: 10 low-risk new-contributor PRs (kanban/windows/credential-pool/deepseek-aux/etc)
files:
agent/credential_pool.py,cli.py,gateway/platforms/base.py,hermes_cli/kanban.py,plugins/model-providers/deepseek/__init__.py,run_agent.py,scripts/install.ps1,scripts/release.py,scripts/setup_open_webui.sh,tests/plugins/model_providers/test_deepseek_profile.py,tools/delegate_tool.py -
#28416 fix(kanban): honor severity thresholds in diagnostics (#26431)
files:
hermes_cli/kanban_diagnostics.py,plugins/kanban/dashboard/plugin_api.py,tests/hermes_cli/test_kanban_diagnostics.py
4 PRs closed without merging
From the close comments: merged via another change 2 · done elsewhere 1 · other 1
-
#26384 fix(kanban): make `diagnostics --severity` an "at or above" threshold · done elsewhere →
1eadb06,#26661 -
#26431 fix(kanban): honor severity thresholds in diagnostics · merged via another change →
#28416 -
#26559 fix(kanban): severity filter should be >= not exact-match as documented · other →
#26384,#26431 -
#26661 fix(kanban): --severity filter uses >= comparison per documented behavior · merged via another change →
#27292
Closed issues · 1
- Closed#26379hermes kanban diagnostics --severity filter is exact-match, not "at or above" as documented (kanban.py:1406)
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.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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