@=j zdZddlmZddlZddlmZmZddlmZGddeZ d d Z Gd d e Z dS)u"CronScheduler provider interface (Axis B — the trigger). ⚠️ EXPERIMENTAL — this interface is validated by exactly ONE consumer (the built-in) until an external provider (Chronos, Phase 4) shakes it out. Until then the module path, method signatures, and start() kwargs MAY change without a deprecation cycle. Once a second provider validates the shape it becomes stable. Any growth MUST be additive (new optional method with a default), never a changed signature on start() or a new abstractmethod. A CronScheduler decides *when* a due job fires. It does NOT decide what firing means: execution + delivery stay in cron.scheduler.run_job / _deliver_result, shared by all providers. Providers must never reimplement agent construction or delivery. The built-in InProcessCronScheduler runs the historical 60s daemon-thread ticker. Alternative providers (e.g. Chronos, a NAS-mediated managed-cron provider for scale-to-zero deployments) live under plugins/cron_providers// and are selected via the `cron.provider` config key (empty = built-in). ) annotationsN)ABCabstractmethod)AnyceZdZdZeeddZddZedddd ddZddZ ddZ dddddZ ddZ dS) CronScheduleruAxis-B trigger provider. Decides WHEN a due cron job fires. Required surface is intentionally minimal: ``name`` + ``start``. ``stop`` and ``is_available`` carry safe defaults. The three Phase-4 hooks (``on_jobs_changed`` / ``fire_due`` / ``reconcile``) are added later as NON-abstract methods so the built-in keeps satisfying the ABC without overriding them — see ``test_abc_growth_stays_additive``. returnstrcdS)z,Short identifier, e.g. 'builtin', 'chronos'.Nselfs =/home/rurouni/.hermes/hermes-agent/cron/scheduler_provider.pynamezCronScheduler.name%boolcdS)a)Whether this provider can run in the current environment. MUST NOT make network calls. The built-in is always available; an external provider checks for configured endpoint/credentials. When a named provider returns False, the resolver falls back to the built-in. Tr r s r is_availablezCronScheduler.is_available*s trN<adaptersloopinterval stop_eventthreading.EventrrrrintNonecdS)aPBegin firing due jobs. For the built-in this BLOCKS in the 60s loop until stop_event is set (it is run inside a daemon thread by the caller, exactly as today). An external provider may register a schedule/webhook and return immediately; in that case it must still honor stop_event for teardown. Nr )rrrrrs rstartzCronScheduler.start3rrcdS)zOptional eager teardown hook. Default no-op; setting the stop_event is the primary stop signal. Override for providers holding external resources (queue consumers, HTTP servers).Nr r s rstopzCronScheduler.stopD trcdS)aCalled after a successful store mutation (create/update/remove/ pause/resume). External providers reconcile their registry here (e.g. Chronos re-provisions/cancels the affected one-shot via NAS). Built-in: no-op (it re-reads jobs.json on every tick).Nr r s ron_jobs_changedzCronScheduler.on_jobs_changedNs trrrjob_idcrddlm}m}ddlm}||sdS||}|dS||||S)aLRun a single job NOW via the shared orchestrator. Called by the inbound fire webhook when an external scheduler signals a job is due. The default claims the job with a store-level compare-and-set (multi-machine at-most-once), then runs it via the shared ``run_one_job`` body. Built-in never calls this (it has its own tick loop); an external provider routes its inbound fire here. Returns True if THIS caller claimed and ran the job, False if the claim was lost (another machine/retry won it) or the job no longer exists. r)claim_job_for_fireget_job) run_one_jobFNr&) cron.jobsr)r*cron.schedulerr+)rr'rrr)r*r+jobs rfire_duezCronScheduler.fire_dueUst :9999999......!!&)) 5gfoo ;5{3====rcdS)zConverge the external registry toward jobs.json (the desired state): arm missing one-shots, cancel orphaned ones, re-arm changed times. Built-in: no-op.Nr r s r reconcilezCronScheduler.reconcilekr#rr r )r r) rrrrrrrrr r)r r)r'r rrrrr r) __name__ __module__ __qualname____doc__propertyrrrr r"r%r/r1r rrrrs;;;^X;       ^ 8<>>>>>>,rrr 'CronScheduler'c|ddl}|d}d} ddlm}m}||dddpd}n#t $rYnwxYw|r|d vrtS dd lm }||}|$| d |tS| s$| d |tS| d |j |S#t $r/}| d||tcYd}~Sd}~wwxYw)u1Return the active cron scheduler provider. Reads ``cron.provider`` from config. Empty/absent → built-in. A named provider that is missing, fails to load, or reports ``is_available() == False`` falls back to the built-in with a warning — cron must never be left without a trigger. rNcron.scheduler_provider)cfg_get load_configcronprovider)default)builtinz in-process inprocess)load_cron_schedulerz3cron.provider '%s' not found; using built-in tickerz7cron.provider '%s' not available; using built-in tickerz!Using cron scheduler provider: %sz=Failed to load cron.provider '%s' (%s); using built-in ticker)logging getLoggerhermes_cli.configr<r=strip ExceptionInProcessCronSchedulerplugins.cron_providersrCwarningrinfor)rDloggerrr<r=rCr?es rresolve_cron_schedulerrOrsNNN   8 9 9F D :::::::: vz2FFFL"SSUU       (4AAA%'''(>>>>>>&&t,,   NNPRV W W W)++ +$$&& , NNTVZ [ [ [)++ + 7GGG ((( KTST   &'''''''' (s;3A AA66D-7D%D D; $D60D;6D;c:eZdZdZed dZdddddZdS) rIzDefault provider: the historical in-process 60s ticker. ``start()`` blocks in the tick loop until ``stop_event`` is set, identical to the pre-refactor ``_start_cron_ticker`` core loop. The caller runs it in a daemon thread. r r cdS)NrAr r s rrzInProcessCronScheduler.namesyrNrrcddl}ddlm}ddlm}|d}|d|||s{d} |d||dd} n/#t$r"} | d | d Yd} ~ nd} ~ wwxYw|| | ||ydSdS) Nr)tick)record_ticker_heartbeatr:z0In-process cron scheduler started (interval=%ds)F)verboserrsyncTzCron tick error: %s)exc_info)success) rDr-rSr,rTrErLis_set BaseExceptionerrorwait) rrrrrrD cron_tickrTrMokrNs rr zInProcessCronScheduler.startsG444444555555""#<== FQQQ !!!##%% &B F %(ERRRR  F F F 2A EEEEEEEE F $ #B / / / / OOH % % %%##%% & & & & &sA// B9BBr2)r3r4r5r6r7rr r rrrIrIs`X-1tb&&&&&&&rrI)r r8) r6 __future__r threadingabcrrtypingrrrOrIr rrrcs&#"""""########TTTTTCTTTn%(%(%(%(P(&(&(&(&(&](&(&(&(&(&r