Callable api_key breaks custom provider resolution
NousResearch/hermes-agent · cluster 88667 · agent
Data as of
Nothing open on GitHub. Fix merged in #113969. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113969. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114333. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where a callable api_key causes an AttributeError during custom provider resolution, along with fixes to guard against this in auth and agent code paths.
Open issues0
Open PRs0
Fixes on record
-
#113969 fix(aux): async aux calls to named custom providers keep their key_cmd bearer and extra_headers (#109595, salvage #109626)
files:
agent/auxiliary_async_rebuild.py,agent/auxiliary_client.py,tests/agent/test_auxiliary_named_custom_providers.py -
#114333 A callable key_cmd credential survives every auxiliary custom-provider branch (#88667, credit #107344)
files:
agent/auxiliary_client.py,contributors/emails/[redacted:email],tests/agent/test_command_token_source.py
4 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1 · superseded by another PR 1 · other 1
-
#88668 fix(auth): keep callable api_key intact when resolving a custom provider · merged via another change →
#88667,#114333 -
#89106 fix(agent): guard callable api_key in resolve_provider_client (#88667) · duplicate →
#88668 -
#105595 fix(auth): keep a callable key_cmd credential in the api_key branch · other →
#114333 -
#107344 fix(aux): keep callable key_cmd credentials intact in all custom-provider resolution branches · superseded by another PR →
#114333,#113969
Closed issues · 1
- Closed#88667[Bug]: callable api_key from key_cmd crashes custom-provider resolution with AttributeError
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.29: 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 Lab