mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-28 18:19:28 +00:00
d7488a5579
The identity-refresh TTL used 0.0 as the "never checked" sentinel and compared it against time.monotonic(). That epoch is arbitrary and starts near zero on a freshly-booted host, so on CI runners and containers `monotonic() - 0.0` was itself below the TTL — "never checked" read as "checked just now" and the first identity refresh was suppressed for the first 5 minutes of uptime. The stale-handle recovery therefore did nothing on exactly the machines most likely to be freshly booted. Invisible on a long-lived dev box (uptime >> TTL); caught by CI. - Sentinel is now None, meaning never checked and always stale. - Both TTL comparison sites route through _bot_identity_is_fresh(). - Regression test pins the invariant under a faked 12s-uptime clock. Verified by re-running the recheck tests against a simulated 3s-uptime host: green with the fix, and restoring the 0.0 sentinel reproduces the exact CI failure locally. |
||
|---|---|---|
| .. | ||
| browser | ||
| context_engine | ||
| cron_providers | ||
| dashboard_auth | ||
| disk-cleanup | ||
| google_meet | ||
| hermes-achievements | ||
| image_gen | ||
| kanban | ||
| memory | ||
| model-providers | ||
| observability | ||
| platforms | ||
| security-guidance | ||
| spotify | ||
| teams_pipeline | ||
| video_gen | ||
| web | ||
| __init__.py | ||
| plugin_utils.py | ||