Cairn
NousResearch/hermes-agent

Same-provider fallbacks skipped when pool lacks wait information

Cluster 140568 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

The members describe one theme: a candidate pool whose next_available_at() returns None is treated as exhausted, which causes same-provider fallbacks to be skipped (reported with Vertex SA credentials). Two pull requests propose changing this handling and one bug report describes the behavior; their outcomes are not stated in the titles.

Open issues1

  • Issue#140568[Bug]: Same-provider fallbacks always skipped — _candidate_pool_exhausted treats next_available_at()=None as exhausted (Vertex SA credentials)

Open PRs1

  • PR#140615fix(agent): treat a pool with no wait information as unexhausted for fallback

1 PR closed without merging

From the close comments: other 1

  • #140613 fix(agent): stop skipping same-provider fallbacks when the pool has no wait information · other → #140893, #140849, #140808, #140236, #139530
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/140568.json
cluster/140568.md