+ jHàj ãó2€RtRRRRRR/RRlltRRltR#) z@Job-level visibility for a recovered, acknowledged worker death.ÚerrorNÚadaptersÚloopcó0€V^8„dQhR\R\/#)éÚjobÚreturn)ÚdictÚbool)Úformats"ÚB/home/ubuntu/.hermes/hermes-agent/cron/scheduler_worker_failure.pyÚ __annotate__r s€÷)ñ)Ü ð)ä ñ)óc ó΀^RIHp^RIHpVP \ VR,44pV'dVP R4R8wdR#VP R4p\V\4'd%\ VP R4;'gR 4MR pV'gR#VPVR ,VR 7;_uu_4p V 'g R R R 4R #T;'g VR,pVPPRVR ,V4VP4p R p VPWW#R7wr¼VPV 4VP!VR ,RV3RV RV/V!V4'dRR /M/BR R R 4R # TPT 4TP!TR ,RT3RT RT/T!T4'dRR /Bi/Bi;i +'giR #;i)a'Project only this fire's uncertain outcome, without retrying its side effects. A terminal ledger row alone does not retire the job claim or notify its owner. Fence the notice and bookkeeping together so recovery cannot overwrite a newer fire or duplicate a failure the worker already recorded. )Ú scheduler)Ú is_retry_runÚ execution_idÚstatusÚunknownFÚ fire_claimÚbyÚÚid)Úexpected_ownerNTrz Job '%s': %s)rrÚdelivery_errorÚexpected_fire_ownerÚ ladder_rung)ÚcronrÚcron.unreachable_retryrÚ get_executionÚstrÚgetÚ isinstancer Úfire_claim_fenceÚloggerrÚ_install_fire_secret_scopeÚ_deliver_crash_failureÚ_reset_fire_secret_scopeÚ mark_job_run) rrrrrrÚ executionÚclaimÚownerÚ owns_claimÚ scope_tokensrÚ_s &$$$ r Úrecord_unknown_worker_outcomer/sá€õÝ3à×'Ñ'¬¨C°Õ,?Ó(@ÓA€Iß ˜ Ÿ ™  hÓ/°9Ô<ÙØ G‰GLÓ !€EÜ*4°U¼D×*AÒ*AŒC— ‘ ˜$“×%Ð% 2Ô &Àr€Eß ÙØ × #Ñ # C¨¥I¸eÐ #× DÔ DÈ ßØ÷ EÑ Dð×+Ð+˜ 7Õ+ˆØ×Ñ×ј~¨s°4­y¸%Ô@Ø ×;Ñ;Ó=ˆ ؈ð Ø )× @Ñ @Ø Xð!Aó!Ñ ˆNð × .Ñ .¨|Ô <Ø × "Ò "ØD• ØØñ ð .ð  ð %*ð  ñ-9¸×,=Ò,=M 4Ñ(À2ó ÷ Eñ, øð × .Ñ .¨|Ô <Ø × "Ò "ØD• ØØñ ð .ð  ð %*ð  ñ-9¸×,=Ò,=M 4Ð(ó ðDFó ú÷ EÖ Dñ, ús3à GÃGÃ$AGÄ%FÄ:AGÆAGÇGÇ G$ có>€V^8„dQhR\R,R\/#)rÚ returncodeNr)Úintr )r s"r r r 0s€÷ ñ ¬c°D­jð ¼Sñ rcó€RV R2#)uÀCause for an attempt whose restart-safe worker this process watched exit. The generic dead-owner sweep can only say the owner vanished, so it names a scheduler restart — but this waiter never lost its scheduler: it handed the attempt to the external worker and then saw that worker exit with this status. The run is still ``unknown`` rather than ``failed`` (whether side effects ran is still unknown); only the cause becomes truthful (#128509). z,Restart-safe cron worker exited with status zn after adopting this execution, without writing a durable terminal state; whether side effects ran is unknown.©)r1s&r Úexternal_worker_exited_reasonr50s€ð 7°z°lðCð ðr)Ú__doc__r/r5r4rr Úr7s+ðÙFð)Øð)Ø'+ð)Ø26÷)÷X r