Skip to content

fix(config): recognize cron script timeout - #78503

Closed
daxro wants to merge 1 commit into
NousResearch:mainfrom
daxro:fix/recognize-cron-script-timeout
Closed

fix(config): recognize cron script timeout#78503
daxro wants to merge 1 commit into
NousResearch:mainfrom
daxro:fix/recognize-cron-script-timeout

Conversation

@daxro

@daxro daxro commented Aug 4, 2026

Copy link
Copy Markdown

Summary

  • Add cron.script_timeout_seconds to the recognized cron configuration defaults.
  • Cover hermes config set cron.script_timeout_seconds 600 with a regression test.

Test plan

  • uv run --extra dev pytest tests/hermes_cli/test_set_config_value.py -q
  • Temp-home CLI check: hermes config set/get cron.script_timeout_seconds

@alt-glitch alt-glitch added type/bug Something isn't working comp/cli CLI entry point, hermes_cli/, setup wizard comp/cron Cron scheduler and job management area/config Config system, migrations, profiles P2 Medium — degraded but workaround exists sweeper:risk-compatibility Sweeper risk: may break existing users, config, migrations, defaults, or upgrades labels Aug 4, 2026
@teknium1

Copy link
Copy Markdown
Contributor

Merged via PR #85536 (rebase-merge) — your commit was cherry-picked onto current main with your authorship preserved in git log.

cron.script_timeout_seconds is now a recognized config key, and the mislabeled script-timeout delivery you flagged is fixed in the same PR via #82460's contract check. Thanks!

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 comp/cron Cron scheduler and job management P2 Medium — degraded but workaround exists sweeper:risk-compatibility Sweeper risk: may break existing users, config, migrations, defaults, or upgrades type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants