yeyitech ec27f0a3fa fix(cron): fall back gracefully when HERMES_CRON_TIMEOUT is invalid ... Bare `float(os.getenv("HERMES_CRON_TIMEOUT", 600))` in `run_job()` raises a `ValueError` when the env var is set to a non-numeric string (e.g. "abc"). Replace it with the same defensive try/except pattern already used by `_get_script_timeout()` for `HERMES_CRON_SCRIPT_TIMEOUT`: log a warning and fall back to the 600 s default instead of crashing. Also update the existing env-var tests to exercise the new code path and add two new tests — one for an invalid value, one for an empty string. Fixes #11319 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-04-29 08:21:04 -07:00
..
__init__.py	docs: clarify gateway service scopes (#1378)	2026-03-14 21:17:41 -07:00
jobs.py	refactor: consolidate symlink-safe atomic replace into shared helper	2026-04-28 04:58:22 -07:00
scheduler.py	fix(cron): fall back gracefully when HERMES_CRON_TIMEOUT is invalid	2026-04-29 08:21:04 -07:00