Fix scalar hook event values treated as char lists

NousResearch/hermes-agent · cluster 11902 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 2 PRs.

These issues and PRs address a bug where scalar (string) event values in hook/manifest YAML configurations were being iterated character-by-character instead of treated as a single-item list. Fixes involve normalizing scalar event values to a proper single-item list.

Open issues1

  • Issue#11902Hook loader mis-registers scalar HOOK.yaml events values character-by-character

Open PRs2

  • PR#37486fix(gateway/hooks): normalize scalar events to single-item list
  • PR#124383fix(gateway): a scalar or malformed HOOK.yaml events value no longer breaks hook loading (salvage #37486)

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #11944 fix(hooks): reject scalar manifest events · other → #11902
  • #39799 fix(gateway/hooks): normalize scalar events string to list (#11902) · duplicate → #37486
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.40: 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
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.