Fix registry default for pool entries missing base_url
Cluster 116800. Data as of
Nothing open on GitHub. Fix merged in #117559 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117559. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117559. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where switching models errors when a credential pool entry has no base_url, because the registry default endpoint is not correctly looked up in that case.
Open issues0
Open PRs0
Fixes on record
-
#117559 fix(runtime): pooled credentials without a base_url resolve the provider endpoint on model switch (#116800, salvage #116843)
files:
hermes_cli/runtime_provider.py,tests/hermes_cli/test_pool_missing_endpoint.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#117337 fix(runtime): resolve the registry default when a pool entry has no base_url · done elsewhere →
23d3eda,#117559
Closed issues · 1
- Closed#116800Model switch fails with 'no base_url resolved' when the selected credential-pool entry lacks base_url
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.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
- Merged PRs
- #117559
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026