`gj&dZddlmZddlZddlZddlmZmZmZddl m Z ejdZ ddd d Z Gd d e Zdd Zy)u"Chronos — NAS-mediated managed cron provider (scale-to-zero). Chronos (the Greek god of time, alongside Hermes) is the first non-default ``CronScheduler``. It lets a hosted gateway scale to zero while idle and still fire cron jobs: instead of a 60s in-process ticker, it asks NAS to arm exactly one external one-shot per job at that job's real next-fire time. NAS calls the agent back at fire time over an authenticated webhook (``/api/cron/fire``); the agent runs the job via the shared ``run_one_job`` body and re-arms the next one-shot. The external scheduler NAS uses is an internal NAS implementation detail — Chronos names no vendor, holds no scheduler credentials, and speaks only to NAS's ``agent-cron`` endpoints with the agent's existing Nous token. Design constraints (see the plan's DQ-1): - start() arms all enabled jobs and RETURNS; it never blocks and never spawns a periodic wake. Between fires the machine is truly at zero. - reconcile runs only on a warm process (start / on_jobs_changed / piggybacked on a fire), never as a periodic wake of a sleeping machine. Inert unless ``cron.provider: chronos``. ``resolve_cron_scheduler`` falls back to the built-in if Chronos is unavailable, so cron never loses its trigger. Wire contract: ``docs/chronos-managed-cron-contract.md``. ) annotationsN)AnyDictOptional) CronSchedulerz cron.chronos)defaultcX ddlm}m}||g|d|iS#t$r|cYSwxYw)z0Read a cron.chronos.* config value (no network).r)cfg_get load_configr )hermes_cli.configr r Exception)r keysr r s Z/root/.hermes/venv/lib/python3.12/site-packages/plugins/cron_providers/chronos/__init__.py_cfgr&s5:{}=t=W== s  ))ceZdZdZddZeddZddZddZdZ ddZ ddd d d Z dd Z dd Z ddZddZddZddZddddfdZxZS)ChronosCronSchedulerz$NAS-mediated external cron provider.cRi|_tj|_d|_yN)_armed threadingLock_lock_clientselfs r__init__zChronosCronScheduler.__init__2s ') ^^%  cy)Nchronosrs rnamezChronosCronScheduler.name<srcXtdddr tdddsy|jS)uDConfig presence only — NO network. Chronos needs a portal base URL, the agent's own publicly-reachable callback URL (for NAS→agent fires), and a usable Nous token (the agent is logged into the portal). If any is missing, resolve_cron_scheduler falls back to the built-in ticker. cronr portal_url callback_urlF)r_have_nous_tokenrs r is_availablez!ChronosCronScheduler.is_available@s.VY 5$vyR`:a$$&&rcz ddlm}|dxsi}t|jdS#t$rYywxYw)u"True if the agent has a Nous Portal login (no network call). Checks the stored auth state for a Nous access token — does NOT refresh or hit the network (is_available must stay offline). The actual refresh-aware token is resolved lazily at provision time. r)get_provider_auth_statenous access_tokenF)hermes_cli.authr*boolgetr)rr*states rr'z%ChronosCronScheduler._have_nous_tokenLs?  ?+F39rE .12 2  s +. ::cn|jddlm}|tddd|_|jS)N) NasCronClientr$r r%)r _nas_clientr3r)rr3s r _get_clientz ChronosCronScheduler._get_client\s. <<  2(fi)NODL||rc6ttdddxsdS)Nr$r r&r)strrrs r _callback_urlz"ChronosCronScheduler._callback_urlbs4 >:@bAArN<)adaptersloopintervalc|j |jy#t$r }tj d|Yd}~yd}~wwxYw)uArm all enabled jobs via NAS, then RETURN immediately. Does NOT block and does NOT spawn a 60s wake (DQ-1) — that is the whole point of scale-to-zero. The machine wakes only on a NAS→agent fire. z$Chronos start() reconcile failed: %sN)recover_interrupted reconcilerloggerwarning)r stop_eventr:r;r<es rstartzChronosCronScheduler.startgsD   " F NN  F NNA1 E E Fs# A AA cyrr!rs rstopzChronosCronScheduler.stopwsrc~ |jy#t$r }tjd|Yd}~yd}~wwxYw)uA job was created/updated/removed/paused/resumed — reconcile the NAS registry so the affected one-shot is (re-)armed or cancelled.z,Chronos on_jobs_changed reconcile failed: %sN)r?rr@debug)rrCs ron_jobs_changedz$ChronosCronScheduler.on_jobs_changedzs6 L NN  L LLG K K Ls <7<c|d}|jd}|sy|d|}|jj|||j||j5||j |<dddy#1swYyxYw)aAsk NAS to arm exactly one one-shot at the job's next_run_at. The agent computes the time; NAS+its scheduler are the dumb executor. Idempotent per (job_id, fire_at) via dedup_key, so re-arming the same fire is a no-op NAS-side. id next_run_atN:)job_idfire_atagent_callback_url dedup_key)r/r5 provisionr8rr)rjobrNrOrQs r _arm_one_shotz"ChronosCronScheduler._arm_one_shotsT''-( hay)  $$#113 % ZZ *")DKK  * * *s A77BcD |jj||j5|jj |ddddy#1swYyxYw#|j5|jj |ddddw#1swYwxYwxYw)N)rN)r5cancelrrpop)rrNs r_cancelzChronosCronScheduler._cancels| .     % %V % 4 . - . . . . - . . .s. A AA B-B BB Bc |j5|jrt|jcdddS ddd |jj Dcic])}|j dr|d|j dd+}}|j5|jj |ddd|S#1swYxYwcc}w#1swY|SxYw#t$r"}tjd|icYd}~Sd}~wwxYw)uObserved armed one-shots: job_id → fire_at. Prefer the in-memory map (warm process); on a cold/empty map, ask NAS (best-effort). If NAS list fails, return what we have — reconcile then re-arms desired jobs idempotently. NrNrOrz9Chronos _list_armed failed (will re-arm idempotently): %s) rrdictr5 list_armedr/updaterr@rH)ritemobservedrCs r _list_armedz ChronosCronScheduler._list_armedsZZ ){{DKK( ) ) ) !,,.99;88H%XB 77H  - ""8, -O ) )  -O  LLTVW XI sY!C C"".CC"C: C"C C"CC"C"" D +DD D cddlm}|Dcic]A}|jdr.|jdr|jddk7r |d|dC}}|j}|j D]=\}}|j||k7sddlm}||}|s, |j |?t|jD]}||vs |j|y cc}w#t$r!} tjd || Yd } ~ d } ~ wwxYw#t$r!} tjd || Yd } ~ td } ~ wwxYw) z~Converge the NAS-armed one-shots toward jobs.json (desired state): arm missing / re-arm changed-time, cancel orphaned.r) load_jobsenabledrLr0pausedrKget_jobz Chronos failed to arm job %s: %sNz&Chronos failed to cancel orphan %s: %s) cron.jobsrar/r_itemsrerTrr@rAlistrrX) rrajdesiredr^rNrOrerSrCs rr?zChronosCronScheduler.reconcilesK ([# uuYAEE-$8QUU7^x=W dGQ}% %# # ##% '}} VOFG||F#w.-foV**3/ V8==?+ XFW$XLL( X)# %V'I6STUUV!XNN#KVUVWWXs6AC.%C3D 3 D<DD E )EE r:r;ct||||}|rFddlm}||}|r6|j dr%|j dr |j ||S|S#t $r"}tjd||Yd}~|Sd}~wwxYw)uaRun the due job (claim + run_one_job via the ABC default), then re-arm the NEXT one-shot through NAS. Re-arm happens AFTER the run so next_run_at reflects the completed fire. If the job is gone (one-shot completed / repeat-N exhausted), get_job returns None → nothing to re-arm (the schedule naturally stops). rkrrdrbrLz.Chronos failed to re-arm job %s after fire: %sN) superfire_duerfrer/rTrr@rA) rrNr:r;ranrerSrC __class__s rrnzChronosCronScheduler.fire_duesgvtD  )&/Cswwy)cggm.D`&&s+ s !`NN#SU[]^__ `s A B 'BB returnNone)rrr7)rrr.)rSzDict[str, Any]rrrs)rNr7rrrs)rrzDict[str, str])rNr7r:rr;rrrr.)__name__ __module__ __qualname____doc__rpropertyr"r(r'r5r8rDrFrIrTrXr_r?rn __classcell__)rps@rrr/su. '   B -1tb F L**.2XD8<rrc6|jty)uPlugin entrypoint — register the Chronos provider with the loader. Mirrors the memory-plugin shape; plugins/cron_providers discovery calls this and collects the provider via register_cron_scheduler. N)register_cron_schedulerr)ctxs rregisterr}s  4 67r)rr7r rrrrrq)rw __future__rloggingrtypingrrrcron.scheduler_providerr getLoggerr@rrr}r!rrrsN4#&&1   > *%'}=}@8r