+ WjfRa0t$Rt^RIHt^RIt^RIt^RIHt^RIH t H t ^RI H t ]P!]4t]!4tR]R&/tR]R &R R R R RR/tRtRtRtRtRRltRRltRR/RRlltRR/RRlltRRlt!R R!]4tR"R#lt R$R%lt!R&R'lt"R(R)lt#R#)*aWhat Hermes does when an existing ``config.yaml`` cannot be read or parsed. Readers fail open (``{}`` / defaults / last-known-good) so a broken file never takes the process down; this module makes that fallback loud (one warning per file signature, a ``corrupt`` backup), remembers the failure for :func:`get_active_config_parse_failure`, and marks every fallback as a :class:`FailedConfigRead` so the writers refuse to persist it. ) annotationsN)Path)AnyOptional)file_signatureset_CONFIG_PARSE_WARNEDdict_CONFIG_PARSE_FAILURESzlast-known-goodzqHermes is running on the settings it loaded before the edit until it is fixed, so recent changes are not applied.zlast-known-good-backupzbHermes is running on your last good settings until it is fixed, so recent changes are not applied.z refuse-writez7Nothing was written, so the existing file is preserved.zdHermes is running on default settings until it is fixed, so none of your saved settings are applied.zOOpen it with `hermes config edit`, fix {where}, then run `hermes config check`.z0Fix the file permissions or move it aside first.zFix it with `hermes config edit` and check with `hermes config check`, or copy the newest good file from {backups} over config.yaml.c V^8dQhRRRR/#exc Exceptionreturnstr)formats"QC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_cli\config_read_errors.py __annotate__r+s??i?C?c\VRR4;'g\VRR4p\VRR4p\V\4'd RV^, 2#R#)z@``"line 12"`` from a PyYAML problem mark (1-based), else ``""``. problem_markN context_marklinezline )getattr isinstanceint)rmarkrs& r_yaml_error_locationr +sQ 3 - S Snd1SD 4 &D!+D#!6!6U4!8* >B>rc V^8dQhRRRR/#r r)rs"rrr2s""Y"3"rc\VRR4pV'dT M\V4P4pRPVP 44#)zQSingle-line ``Details:`` text: the PyYAML problem, or the exception's first line.problemN )rrstripjoinsplit)rr#texts& r_yaml_error_detailsr)2s;c9d+G"gYC(8D 88DJJL !!rfallbackdefaultsc(V^8dQhRRRRRRRR/#)r config_pathrrrr*rrr)rs"rrr9s0 e eT e ePS eeh erc\V4pV'dRV 2MRp\PV\4p\ V\ 4'dRV RV R\ V4 2#\PT;'gRR7pRV RV R V RV 2#) zUser copy for an unparseable config.yaml: what happened, what Hermes is doing, how to fix. Only the problem line/column is printed; the raw PyYAML text goes to a ``Details:`` line.z at rYour settings file (z) could not be read. r$z the problem)wherez) has a formatting errorz. ) r _PARSE_FAILURE_FALLBACK_MSGget_PARSE_FAILURE_DEFAULTS_MSGrOSError_read_error_fix_PARSE_FAILURE_REPAIR_MSGr)r-rr*r0at fallback_msgrepairs&&$ rformat_config_parse_failurer:9s ! %E 4wbB.228=XYL#w%k]2G ~UVWfgjWkVlmm & - -E4J4J] - KF !+.Frd"\NZ[\b[c ddrc(V^8dQhRRRRRRRR/#) r r-rrrr*rrNoner)rs"rrrEs,   % 47 IM rcVP4p\V4p\V4.VO5p.VO\V4N5\\V4&V\ 9dR#\ P V4^RIHp\V\4'dRMV!VR4p\WVR7pVeVRV R2, p\PRV\V44\PP!RV R \V4 R 24\PP#4R# \d\T4^^^^3pLi;i \$dR#i;i) uSurface a config.yaml parse failure to log and stderr (once per file signature). Silent fallback to ``DEFAULT_CONFIG`` drops every user override, so this must be loud. ``fallback`` selects the message wording: ``"defaults"`` (fresh process, nothing else to serve) or ``"last-known-good"`` (in-process retention of the previously loaded config — see the codex#31188 port in ``hermes_cli.config._load_config_impl``). N) backup_configcorrupt)r*z( A copy of the broken file was saved to .z%s Details: %su⚠️ hermes config: z Details:  )statrrr r4raddhermes_cli.config_backupsr>rr:loggerwarningr)sysstderrwriteflushr) r-rr*stsigkeyr> backup_pathmsgs &&$ r_warn_config_parse_failurerPEs?-    R ;&#&3CS3C#c(3Cs;/0 ""S!7$S'22$ kS\8]K %k JC 9+aHH NN#S*=c*BC  23%GZ[^G_F``bcd  -;Aq!,-    s%A D#A E#EE EEcV^8dQhRR/#)r rz Optional[str]r)rs"rrrfs   rc^RIHp\\V!4;p4,pVP 4p\ V4VR,8Xd V^,#R# \ dR#i;i)zReturn the recorded parse error while the ACTIVE config.yaml is still byte-identical (mtime_ns + size + ino + ctime_ns) to the file that failed to parse; else None.)get_config_path:NNN)hermes_cli.configrSr rrBrr)rSpathrecordrKs rget_active_config_parse_failurerXfs_2'O4E,ED(FG YY[*2.&*\V\4'd\#R#)z9Try again; run `hermes config check` if it keeps failing.)rPermissionError _FIX_PERMS)rs&rr5r5~s #C99:ECErc$V^8dQhRRRRRR/#)r r-rr\rrr<r)rs"rrrs&ffTfffrc \V\4'gR#VPp\V\4'd\ VRV\ V44h\ VRV\ P\4R74h)zWRefuse to save a fallback; only a read error is worth retrying, bad YAML needs an edit.Nzcould not be readzhas a formatting error)backups) rrZrbr4_refuse_overwriter5 _FIX_YAMLr_backups_dir_display)r-r\rs&& r_refuse_failed_readrwsl d, - - //C#w -@#WZG[\\ -sI4D4DMaMc4D4d ffrc ,V^8dQhRRRRRRRRRR /#) r r-rreasonrrrfixr RuntimeErrorr)rs"rrrs0004009030S_0rc |\V4pV'dRV R2MRp\RV RV V RV R\V4 2 4#)z[Error for a write that must not replace an existing config.yaml. Plain lead + ``Details:``.z ()rr/z) z , so this change was not saved. z Details: )r r{r))r-ryrrzr0r7s&&&& rrtrtsZ  %E2eWARB  {m2fXbT9YZ]Y^_',- / 00rcV^8dQhRR/#)r rrr)rs"rrrs66c6rc"^RIHpV!4 R2#)display_hermes_homez/backups/config/)hermes_constantsrrs rrvrvs4!# $$4 55r)$__conditional_annotations__rj __future__rloggingrGpathlibrtypingrrutilsr getLoggerrfrErr__annotations__r r1r3r6rprur r)r:rPrXr rZr5rwrtrv)rs@rrs#    8 $ Ec! "!KCMO km ? , ?" eV` e :D B   t  E f06r