NousResearch/hermes-agent
Slack bot silently disabled by config regression
Cluster 16682 · gateway. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 2 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
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA regression caused the Slack integration to be silently disabled when a top-level 'slack:' block exists in config.yaml without an explicit 'enabled' field. The cluster covers the bug reports and fixes addressing this opt-in/enabled handling.
Open issues0
Open PRs0
1 PR closed without merging
From the close comments: done elsewhere 1
-
#16738 fix(gateway): treat yaml slack block without explicit enabled as opt-in (#16682) · done elsewhere →
49fb754
Closed issues · 2
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.45: 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 2
- Attempts
- 1 PR closed without merging