Skip to content

fix(config): add request_timeout_seconds and stale_timeout_seconds to provider _KNOWN_KEYS (#16779)#16812

Closed
vominh1919 wants to merge 1 commit into
NousResearch:mainfrom
vominh1919:fix/add-missing-provider-known-keys-16779
Closed

fix(config): add request_timeout_seconds and stale_timeout_seconds to provider _KNOWN_KEYS (#16779)#16812
vominh1919 wants to merge 1 commit into
NousResearch:mainfrom
vominh1919:fix/add-missing-provider-known-keys-16779

Conversation

@vominh1919

Copy link
Copy Markdown
Contributor

Summary

The provider-entry validator in hermes_cli/config.py has a _KNOWN_KEYS set that's out of sync with both the documented config example and the runtime code. It warns on request_timeout_seconds and stale_timeout_seconds as "unknown config keys ignored" even though those are:

  1. Read at runtimehermes_cli/timeouts.py:40 reads provider_config.get("request_timeout_seconds") and :69 reads provider_config.get("stale_timeout_seconds")
  2. Documentedcli-config.yaml.example shows both keys in the providers: section

Fix

Add both keys to the _KNOWN_KEYS set (one-line change).

File changed: hermes_cli/config.py (+2 lines in set literal)

Impact

Eliminates false warnings for users who configure per-provider timeouts as documented. No behavioral change — the keys already work; this just stops the spurious warning.

Fixes #16779

… provider _KNOWN_KEYS (NousResearch#16779)

The provider-entry validator in hermes_cli/config.py warns on
request_timeout_seconds and stale_timeout_seconds as "unknown config
keys ignored" even though those are valid keys read by
hermes_cli/timeouts.py and documented in cli-config.yaml.example.

Add both keys to _KNOWN_KEYS so the false warning is suppressed.

Fixes NousResearch#16779
@alt-glitch alt-glitch added type/bug Something isn't working P3 Low — cosmetic, nice to have comp/cli CLI entry point, hermes_cli/, setup wizard area/config Config system, migrations, profiles labels Apr 28, 2026
@alt-glitch

Copy link
Copy Markdown
Collaborator

Likely duplicate of #16786 — Same fix: add request_timeout_seconds and stale_timeout_seconds to provider _KNOWN_KEYS. Both fix #16779.

@teknium1

Copy link
Copy Markdown
Contributor

Closing as already fixed on main.

Triage notes (high confidence):
origin/main hermes_cli/config.py:3050 already contains "request_timeout_seconds", "stale_timeout_seconds" in _KNOWN_KEYS — fix already landed.

If you still see this on the latest version, please reopen with reproduction steps.

(Bulk-closed during a CLI triage sweep.)

@teknium1 teknium1 closed this May 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/config Config system, migrations, profiles comp/cli CLI entry point, hermes_cli/, setup wizard P3 Low — cosmetic, nice to have type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provider validator's _KNOWN_KEYS is missing request_timeout_seconds / stale_timeout_seconds

3 participants