Cairn

Handling non-mapping plugin.yaml without crashing

NousResearch/hermes-agent · cluster 14066 · hermes cli

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
6items grouped
Known?
Yes. 6 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 3 PRs.

These issues and PRs concern how the plugin system should behave when a plugin.yaml file contains valid YAML that is not a mapping type, with various proposed approaches including rejecting, ignoring, or tolerating such manifests to prevent a crash.

Open issues1

  • Issue#14066plugins install crashes when plugin.yaml is valid YAML but not a mapping

Open PRs3

  • PR#14086fix(plugins): tolerate non-mapping plugin manifests
  • PR#14147fix(plugins): ignore non-mapping manifests
  • PR#23253fix(plugins): ignore non-mapping plugin manifests

2 PRs closed without merging

From the close comments: stale or abandoned 1 · other 1

  • #14077 fix(plugins): reject non-mapping plugin manifests · stale or abandoned
  • #14122 fix(plugins): treat non-mapping plugin.yaml as invalid instead of crashing · other → #14077, #14086, #14066
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.33: 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
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/14066.json
cluster/14066.md