Cairn
NousResearch/hermes-agent

llamacpp port detection config not forwarded

Cluster 105834. 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, 1 issue 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
Nothing open on GitHub.

These issues and PRs concern a bug where the llamacpp provider fails to detect a running llama-server on non-default ports because the configured detection ports are not properly passed through to the endpoint resolution logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

  • #105837 fix(providers): forward config to resolve_llamacpp_endpoint for detect_ports (#105834) · merged via another change → 2cfb655, 95464a7
  • #105847 fix(llamacpp): honor configured detection ports · duplicate → #105837, #105834
Closed issues · 1
  • Closed#105834llamacpp provider not detected when llama-server runs on a non-default port (detect_ports ignored in _llamacpp_pdef)
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/105834.json
cluster/105834.md