Cairn

Provider config missing timeout keys in validator

NousResearch/hermes-agent · cluster 16779

Data as of

Nothing open on GitHub. Fix merged in #16908. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #16908. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug was identified where request_timeout_seconds and stale_timeout_seconds were absent from the provider validator's _KNOWN_KEYS list. These items track the report and associated fixes to add those keys so provider config entries are accepted without validation errors.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #16908 fix(config): add request_timeout_seconds and stale_timeout_seconds to provider _KNOWN_KEYS

    merged to main

    files: hermes_cli/config.py, tests/hermes_cli/test_provider_config_validation.py

3 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1 · superseded by another PR 1

  • #16786 fix(config): accept request_timeout_seconds / stale_timeout_seconds in providers entries (#16779) · superseded by another PR → #16908, #16853
  • #16812 fix(config): add request_timeout_seconds and stale_timeout_seconds to provider _KNOWN_KEYS (#16779) · done elsewhere
  • #16853 fix(config): add request_timeout_seconds and stale_timeout_seconds to provider _KNOWN_KEYS · merged via another change → #16908
Closed issues · 1
  • Closed#16779Provider validator's _KNOWN_KEYS is missing request_timeout_seconds / stale_timeout_seconds
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.40: 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

Merged PRs
#16908
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
28 Apr 2026

For your agent

The same facts, typed.

cluster/16779.json
cluster/16779.md