hermes-agent/cron
slow4cyl 65d6bd2b9f fix(cron): patched compatibility constants take precedence over a repointed env
Review follow-up: tests that monkeypatch CRON_DIR/JOBS_FILE/OUTPUT_DIR (the
documented process-wide compatibility surface) were bypassed by the lazy
env fallback — 3 file-permission tests, the cross-process lock test, and
the heartbeat roundtrip regressed. _current_cron_store() now snapshots the
constants at import and honors any deliberate re-point of them ahead of
the env resolution, so the precedence is: use_cron_store() override >
patched constants > fresh HERMES_HOME > import defaults. Adds a test
pinning constants-beat-env; the late-env sentinel behavior is unchanged.
tests/cron: failure set byte-identical to unpatched main on this box
(the 5 regressions gone); 138 pass in the touched files.
2026-07-17 16:08:56 +05:30
..
scripts
__init__.py
blueprint_catalog.py
jobs.py fix(cron): patched compatibility constants take precedence over a repointed env 2026-07-17 16:08:56 +05:30
lifecycle_guard.py fix(gateway,cron): guard cron model-tool path + add auto-resume loop breaker (#30719) 2026-07-01 02:48:36 -07:00
scheduler.py fix(cron): robust session title generation (#50535, #50536, #50537) 2026-07-16 22:39:47 -07:00
scheduler_provider.py fix(gateway): quiesce API and cron work during drains 2026-07-13 23:26:10 +05:30
suggestion_catalog.py
suggestions.py