Colon in custom endpoint names causes 404 bug

NousResearch/hermes-agent · cluster 117666 · dashboard

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

A bug where custom endpoint names containing colons (e.g. host:port format) result in permanent 404 errors on use or delete operations. The cluster includes the bug report, a related test, and a fix to preserve colons in custom endpoint IDs during creation.

Open issues1

  • Issue#117666[Bug]: Custom endpoint names containing a colon (e.g. host:port) permanently 404 on Use/Delete

Open PRs2

  • PR#118668fix(config_env): preserve colon in new custom endpoint ids on create (#117666)
  • PR#119283Test custom endpoint activation with colon keys
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.67: 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
dashboard
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.