+ WjKXa0t$Rt^RIHt^RIt^RIt^RIt^RIt^RIt^RI t ^RI t ^RI t ^RI H t HtHt^RIHt^RIHt]P*!R4tRqtRrt]!4tR]R&] P8!4t]!4tR]R &] P8!4t]!4t R]R &] P8!4t!]!4t"R]R &] P8!4t#]!4t$R]R &] P8!4t%]!4t&R ]R&] P8!4t'Rt(RRlt)RRlt*RRlt+RRlt,RRlt-RRlt.RRlt/RsRRlltR R!lt0R"R#lt1R$R%lt2!R&R']Pf4t4]5!0Rtm4t6/t7R(]R)&] P8!4t8]!4t9R]R*&] P8!4t:]!4t;R]R+&] P8!4tR0R1lt?R2R3lt@R4R5ltAR6R7R8R9/R:R;lltBR<R=ltCR>R?ltDR@RAltERBR9/RCRDlltFRERFltGRGRHRIRJRKRL/tHRM]#R ]PRN3RO]'R]PRP3RQ]R]PRR3RS]R ]PRT3RU]%R ]PRV3RW]!R ]PRX3RY]:R*]PRZ3R[]``. ) annotationsN)AnyDictOptional)is_sqlite_wal_reset_vulnerable)is_sqlite_lock_error hermes_statezset[str]_wal_fallback_warned_paths!_wal_delete_fallback_failed_paths_wal_probe_unknown_paths_wal_reset_bug_warned_paths_delete_overridden_warned_pathsset_journal_upgrade_warned_pathsucould not verify journal mode before applying configured journal_mode=delete (database is locked — possible concurrent openers); refusing to downgrade a database this process does not exclusively owncV^8dQhRR/#returnstr)formats"DC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_state_wal.py __annotate__r9sMM3McV'd:V^,e/\V^,4P4P4#R#)zFLower-cased mode from a ``PRAGMA journal_mode`` row, ``""`` if no row.)rstriplower)rows&r_mode_from_rowr9s2*-#a&2D3s1v;    $ $ &L"Lrc V^8dQhRRRR/#)rconnsqlite3.Connectionr Optional[str]r)rs"rrr>s 2}rcR\^4FpVPR4P4pT'd T^,MRp\T\4'dTPR4pTe*\ T4P4P 4u#Ru# \PRX4R# \PdJpR\ T4P 49dRp?R#Tp\P!R4Rp?EKRp?ii;i \dR#i;i)aRead the journal mode from the DB header; ``None`` if undeterminable (new DB, or PRAGMA failed) -> callers take their fail-closed "refuse to downgrade" branch. ``disk i/o error`` can be transient on virtualized block devices (XFS on cloud hosts), so it is retried a few times first.PRAGMA journal_modedisk i/o errorN皙?asciiz:_on_disk_journal_mode: retries exhausted on disk read (%s))rangeexecutefetchonesqlite3OperationalErrorrrtimesleep isinstancebytesdecodeUnicodeDecodeErrorrloggerdebug)r!_rexclast_excmodes& r_on_disk_journal_moder:>s1X ,,45>>@Cs1v$ dE " " {{7+-1,51UZ#-S#"6"6399;   BD,,47%7 sB=B B#"B#c]tRt^tRtRtR#)WalUnsupportedErrora4Raised by :func:`apply_wal_with_fallback` under ``require_wal=True`` when the filesystem cannot provide WAL (SQLITE_PROTOCOL raised, or macOS-NFS silent refusal) or the on-disk mode cannot be verified (probe blocked by a concurrent opener). Subclasses ``OperationalError`` so DB-init handlers still catch it.rN)__name__ __module__ __qualname____firstlineno____doc____static_attributes__rrrrvrvsTrrvzdict[str, bool]_cross_vm_fs_cache_cross_vm_warned_paths#_cross_vm_existing_wal_warned_pathsc$V^8dQhRRRRRR/#)r directoryrmountinfo_pathrr)rs"rrrs"cWZrc\VRRRR7;_uu_4pVP4P4pRRR4R RrTXFpTP R4wrxp TP 4p \ T 4^8g T 'gKAT ^,p RT 9d"T PR R 4PR 4p Y 8Xg0TPT PR 4R ,4'gK\ T 4T8gK\ T 4T P 4^,rTK TP4# +'giEL;i \dR#i;i)zffstype of the longest mount point that is a prefix of ``directory`` (``""`` if unreadable / no match).rzutf-8replace)encodingerrorsNrz - \zlatin-1ignoreunicode_escape/) openread splitlinesOSError partitionsplitlenencoder2 startswithrstripr) rrfhlinesbest_len best_fstypelinefieldsr6tailparts mount_points && r_mountinfo_fstypers .# J JbGGI((*EKk../4  u:> Ah ; %,,YAHHIYZK  #y';';KEE EEc$V^8dQhRRRRRR/#)rrrrrrWr)rs"rrrs'MM3MMY]MrcT\PR8wdR#\W4\9#)zPTrue only when ``directory`` sits on a virtiofs/9p mount per ``mountinfo_path``.linuxF)rErFr_CROSS_VM_FSTYPES)rrs&&r_detect_cross_vm_fsrs" ||w Y 7;L LLrc V^8dQhRRRR/#)rpathrrrWr)rs"rrrs  s t rc\PP\PPV44;'gRp\ ;_uu_4\PT4pRRR4Xf.\T4p\ ;_uu_4T\T&RRR4T#T# \\ 3dR#i;i +'giL[;i +'giT#;i)zaTrue when ``path`` resides on a virtiofs/9p (cross-VM) filesystem; cached per resolved directory.rFN) osrdirnamerealpathrrf_cross_vm_fs_cache_lockr}rpr)rrcacheds& r_path_on_cross_vm_fsrsGGOOBGG$4$4T$:;BBs  ! #'' 2 ! ~$Y/ $ $,2 y )% M6M Z  % $ Ms0AB'B'B? C'B<;B<? C  C# c V^8dQhRRRR/#)rr!r"rrr)rs"rrrs0SrcVPR4P4pV'd"V^,'d\V^,4#R# \P\ \ 3dR#i;i)zIFilesystem path of the ``main`` database, ``""`` for in-memory / unknown.zPRAGMA database_listr)r*r+rr,r- IndexErrorrer`s& r_connection_db_filers[ll12;;=!c!ffs3q6{4"4  $ $j) <s!&A A A A A0/A0c V^8dQhRRRR/#)ractualrrr)rs"rrrsccrc\VR8wd%\P!RT;'gR R24hV#)zIRaise unless SQLite reported ``delete`` for an explicit operator request.rnz2could not set configured journal_mode=delete (got z no result))r,r-)rs&r_verify_configured_deleters6 &&)[\b\q\qfq[rrs'tuu Mrdb_labelzstate.db require_walFc(V^8dQhRRRRRRRR/#)rr!r"rrrrWrr)rs"rrrs7VBVB"4VB3VBbfVBsvVBrcB\PPR4p\\VRR4RR4'dRp\VRR4pVRJ;'dVP RR7pVeV'g\ V4pVR8Xd^\ 4'd&\WR 7V'dVP4##\V4V'dVP4R#R#VR 8XdTV'gL\V4'd;\ 4'd\VRR 7V'dVP4R #R #\4pV'dVP4\ 4'd\YTR 8HR 7#\ T4pTR8Xd+TR 8Xd \T4\T4\T4R#TR 8Xd4Tf\P !\"4h\%\'TR 44#Tf"T'd \)R4h\+RT4R#\-T4pT'dG\/T4'd6T'd \)R4h\+RT4\'TR 4;'gR #\1YY&4# T'dTP4ii;i)uSet ``journal_mode=WAL`` on ``conn``, falling back to DELETE on failure. Returns the mode actually set — or, when the read-only mode probe is blocked by a concurrent opener, ``"wal"`` as the assumed mode with nothing touched (``require_wal=True`` raises instead). Shared by :class:`SessionDB` and ``hermes_cli.kanban_db_connect.connect``. WAL-incompatible filesystems either raise ``OperationalError`` ("locking protocol" / "disk I/O error") or — macOS NFS / SMB / AgentFS — silently refuse and stay in DELETE; either way log ERROR once per process per ``db_label`` and fall back. ``require_wal=True`` raises :class:`WalUnsupportedError` instead. WAL-reset-bug builds (https://sqlite.org/wal.html#walresetbug) never enable WAL on non-WAL files; an already-WAL DB keeps WAL with a warning. Gate deliberately RETAINED: re-measured on the bundled 3.50.4 there is no evidence WAL is safer. Invariant on every path: never downgrade to DELETE if the on-disk header reports WAL or cannot be read — other gateway/cron/worker connections may hold the DB open, and a live downgrade destroys their uncheckpointed commits. An earlier revision of the lock-cancellation fix (#71724) reverted it on the theory that DELETE was "the mode that corrupts", but that comparison was confounded: the clean WAL result came from SQLite 3.53.1, which carries BOTH the WAL-reset fix AND 3.51.0's defenses against close()-broken POSIX locks, so it says nothing about 3.50.4. Re-measured on the actually-bundled 3.50.4 with the lock fix in place, WAL and DELETE are both clean (0/3 each) — i.e. there is no evidence that WAL is safer here, and upstream still documents the WAL-reset bug as real through 3.51.2 with serious consequences. Until a fixed runtime is delivered, keep new databases out of WAL. zhermes_cli.config__spec__N _initializingF _CONFIG_LOCK)blockingrmrrnkept_wal)rrequire_deleteDELETEutcould not verify the on-disk journal mode (database is locked — possible concurrent openers); cannot guarantee WALwal_probe_unknownzvjournal_mode=WAL refused: database is on a cross-VM filesystem (virtiofs/9p) where WAL shared-memory silently corrupts cross_vm_fs)rEmodulesrpgetattracquirer:r_apply_delete_for_wal_reset_bugreleaserTrg_log_wal_reset_bug_oncert&_log_configured_delete_overridden_once!_warn_existing_wal_on_cross_vm_fsr,r-_CANNOT_VERIFY_DELETE_MSGr_set_journal_mode_no_waitrv _log_oncerr _enable_wal) r!rr config_module config_lockacquired current_mode configureddb_files &$$ rapply_wal_with_fallbackrsX.KKOO$78Mw}j$7%PP ->K$&NN;+>+>+>+NH"  "816Lu$133:4S     ! &d+     !  x' @UVZ@[@[133+HuE     ! *+     !&''.tWaemWmnn(.Lu  ! 28 <)$/d#X  **+DE E()B4)RSS %'RS S%x0"$'G'00 %'RS S-*(x8DDHD t{ AAU     ! s*, J8-J? J'J6.J JJc ,V^8dQhRRRRRRRRR R/#) rr!r"rrrrWrr#rr)rs"rrrWs9II(ICIdIZgIloIrcbaaaa aSRJ;'dSR8g;'d \S4oRVVVV3Rllp\SPR4P44pVR8XdV!4#\ RV: R24pV'dVh\ SV4T;'gR# \dh\ PEdp\T4P4o \;QJd#T 3R l\4F 'gK R M R M!T 3R l\44'ghR S 9d\^4Fp\P!R 4SPR4P4p MD \ Pd-p R \T 4P49dhT pRp ? KvRp ? ii;i\T 4R8XdT!4uuRp?#M \S4R9dhT'd\ \T44Th\ ST4\!SR4M \ Pdpp \#RSY{4\SPR4P44p M \ PdRp Mi;iT ;'gRuRp ? uRp?#Rp ? ii;iRp?R#Rp?ii;i)zIFlip a non-WAL, non-vulnerable connection to WAL, or fall back to DELETE.NrmcV^8dQhRR/#rr)rs"rr!_enable_wal..__annotate__]sCrcF<S'd \SS4\S4R#)rm)_log_journal_mode_upgrade_oncerT)r!rrupgrading_existing_dbsr_wal_activated#_enable_wal.._wal_activated]s *8\ Bd#rzPRAGMA journal_mode=WALz0journal_mode=WAL refused without raising (still rrnc3,<"TF qS9xK R#5iNr).0markermsgs& r _enable_wal..rsE/DVS=/DsTFr&r'rwal_delete_fallback_failedr%r)rmN)rgrr*r+rv_log_wal_fallback_oncer,r-rrany_WAL_INCOMPAT_MARKERSr)r.r/r:rr)r!rrrrr9 silent_excr7r6r retry_exc delete_exc read_backrrsff&f @@rrrWsD)4nn9NnnShimSn =dll+DENNPQ 5=!# #(+[\`[ccd)ef  x4x   # #0#hnnsE/DEsssE/DEEE  s "1X 4 ,,'@AJJLC//'s9~/C/C/EE#C  "#&%/)++ ! &- 7  %c#h/S 8x- ) %dH 5'' ) 2Hc N *4<<8M+N+W+W+YZ ++   (( ( ( )a0s5B-.BBJ.?J.`` without waiting on other openers. The ONLY place a non-WAL journal-mode switch may be issued. ``busy_timeout=0`` turns SQLite's exclusivity requirement into a concurrent-opener detector: leaving WAL needs exclusive access, so if ANY other connection holds the DB the pragma fails immediately with ``database is locked`` instead of sneaking the flip between a writer's transactions (how uncheckpointed WAL commits die). Callers must treat a raised ``OperationalError`` as "not exclusively owned: leave the mode alone", never as retryable. Returns the reported mode, ``""`` if no row.zPRAGMA busy_timeoutNzPRAGMA busy_timeout=0zPRAGMA journal_mode=zPRAGMA busy_timeout=) r*r+rdr,r-rerfrrGrH)r!r9rprevious_timeouts&& rrrsll01::<*-#a&2D3s1v;! LL()Ddll-A$+HIRRTU  !9!9 : : LL/0@/AB C; :  $ $i < ; :Z !9!9 : : LL/0@/AB C; : : :sF&CC*D 0C6"C32C36 D -E'6E E' E$ E'c V^8dQhRRRR/#r<r)rs"rrrs77,>747rcn\V4pV'd"\V4'd\RV4R#R#R#)a?#110848: the fresh-DB cross-VM refusal never sees a DB that was already WAL before the check existed (or was created on a native volume and then moved). Keeping WAL is right (never live-downgrade); staying silent is not. Both the vulnerable-SQLite and the regular already-WAL paths return early, so both must call this.cross_vm_fs_existing_walN)rrr)r!rs& rrrs."$'G'00,g61wrrc(V^8dQhRRRRRRRR/#)rr!r"rrrrWrr)rs"rrrs+##*<#3#`d#qt#rc\V4pVR8Xd9\VRR7V'd \V4\V4\ V4R#Vf3V'd\ P !\4h\VRRR7R#Rp\VR4pV'd \V4\VR R7R# \ P dDpT'dh\T4'd \TRRR7T;'gRuRp?#Rp?LuRp?ii;i) uAvoid enabling WAL when the linked SQLite has the WAL-reset bug. Already-WAL on disk: keep WAL (no live downgrade) and warn. Mode unreadable (probe blocked by a concurrent opener): not provably exclusive — leave it and warn; treating "could not read" as "not WAL" once flipped a live WAL state.db to DELETE under a writer, destroying its uncheckpointed commits. Otherwise set DELETE without waiting out openers and warn; an explicit operator request additionally verifies SQLite accepted DELETE.rmTrN)r indeterminaterrrnF) r:rrrrTr,r-rrrr)r!rrcurrentrr7s&$$ rrrs$D)G%48  28 <)$/d# **+DE E4tL F'*4:!&)Hu5   # #'    $ $ #Ht4 P&&h & %'s$ B22D 0D8D:D D cV^8dQhRR/#rr)rs"rrrs v v vrc^RIHpHpHpV!V!44pV!V4pVR9dRV R2#VR8XdRV R2#T# \dR#i;i)z`Repair hint matching what ``hermes update`` can actually do for this install type. See #75153. )detect_install_methodget_project_root%recommended_update_command_for_methodz>Hermes-managed installs can repair the embedded runtime with ``dockerz!update the container image with `zdinstall a Python build bundled with SQLite 3.51.3+ (or backports 3.50.7 / 3.44.6) and restart Hermes>gitunknown)rorrrrr)rrrmethodcmds r_wal_reset_repair_hintrsr vtt&'7'9:3F; ' 'STWSXXYZ Z=Cx=O23%q9XUXX vuvs+= == A  A rujournal mode could not be verified or exclusively switched (database is locked — possible concurrent openers); leaving the journal mode untouched (no live downgrade under concurrent openers)ru\is already in WAL mode — leaving WAL in place (no live downgrade under concurrent openers)rnz1using journal_mode=DELETE instead of enabling WAL wal_reset_bugu %s: linked SQLite %s (interpreter %s) is vulnerable to the WAL-reset corruption bug (https://sqlite.org/wal.html#walresetbug) — %s. Upgrade to SQLite 3.51.3+ (or backports 3.50.7 / 3.44.6); %s. See `hermes doctor`. This warning fires once per process per database.journal_upgradea%s: on-disk journal_mode was %s and has been switched to WAL. This rewrites the database header and persists after this process exits. If %s was a deliberate choice (for example the mitigation for the SQLite WAL-reset bug, or a WAL-unsafe filesystem), setting it with PRAGMA on the file will not survive -- every open re-applies the configured mode. Set `database.journal_mode: delete` in config.yaml to make it stick. This message fires once per process per database. wal_fallbacku%s: WAL journal_mode unsupported on this filesystem (%s) — falling back to journal_mode=DELETE (slower rollback-journal mode; reduces concurrency but works on NFS/SMB/FUSE/ZFS). See https://www.sqlite.org/wal.html for details. This message fires once per process per database.ru%s: both WAL and DELETE journal_mode failed (WAL: %s; DELETE: %s) — continuing with the connection's current journal mode (reads/writes still work). Typically seen on APFS external SSDs under heavy contention. This message fires once per process per database.delete_overriddena%s: database.journal_mode=delete is configured but the on-disk database is already WAL; keeping WAL (a live downgrade under open connections can corrupt the DB). To apply journal_mode=DELETE, stop every Hermes process using this database and run `hermes sessions set-journal-mode delete` (add `--db PATH` for a store other than state.db). This message fires once per process per database.raY%s: could not verify the on-disk journal mode (database is locked / busy); not issuing a journal-mode set-pragma while another connection may hold the file (it could unlink the -wal/-shm sidecars that connection still uses). Leaving the file untouched; this connection inherits the on-disk mode. This message fires once per process per database.ru%s: database directory is on a cross-VM filesystem (virtiofs/9p — typical for Docker Desktop / OrbStack / Podman host bind mounts). SQLite WAL shared-memory is not coherent across the VM boundary and can silently corrupt the database, so journal_mode=DELETE is used instead. To restore WAL concurrency, move the database onto a native volume (e.g. a named Docker volume) instead of a host bind mount. This message fires once per process per database.ruo%s: existing WAL-mode database is on a cross-VM filesystem (virtiofs/9p — typical for Docker Desktop / OrbStack / Podman host bind mounts). SQLite WAL shared-memory is not coherent across the VM boundary and concurrent writers can silently corrupt the database. Hermes does not live-downgrade an on-disk WAL database. Fix one of two ways: stop every Hermes process using this database and run `hermes sessions set-journal-mode delete` (set `database.journal_mode: delete` in config.yaml to keep it), or move the database onto a native volume (e.g. a named Docker volume). This message fires once per process per database.c(V^8dQhRRRRRRRR/#)rkindrrargsrrr=r)rs"rrr=s. U UC U3 Us Ut Urc\V,wr4rV\4V,pT;_uu_4W9d RRR4R#VPV4RRR4\P!WVV.RV4O5!R# +'giL2;i)zEmit ``_ONCE_LOGS[kind]`` once per (process, db_label). Callable *args* are resolved only after the dedupe check, so install-method probes run once.Nc3V"TFp\V4'dV!4MTxK! R#5ir)callable)ras& rr_log_once..Fs*Sd(1++131+Dds')) _ONCE_LOGSglobalsaddr4log)r rrlockset_namelevelmessageseens&&* rrr=sj&0%5"DE 9X D        JJuxT*Sd*ST sA9A99 B c(V^8dQhRRRRRRRR/#)rrrrrWrrr=r)rs"rrrIs/qqcqqTq^bqrc\V'dRM V'dRMR,p\RV\P\P V\ 4R#)zHLog once per (process, db_label) about the WAL-reset vulnerability path.rrrnrN)_WAL_RESET_BUG_ACTIONSrr,sqlite_versionrE executabler)rrractions&$$ rrrIs4 #}OX`*fn oF ox)?)?QWYoprc$V^8dQhRRRRRR/#)rrr previous_moderr=r)rs"rrrOs&IISIIIrc \RWV4R#)zCSingle WARNING per (process, db_label) about a non-WAL -> WAL flip.r N)r)rr$s&&rrrOs -HrOFFNORMALFULLEXTRAzdict[str, int]_SYNCHRONOUS_LEVELSzdict[int, str]_SYNCHRONOUS_NAMESc V^8dQhRRRR/#)r raw_valuerrz Optional[int]r)rs"rrr_src\V\4'd VRJd^#R#\V\4'dV\9dV#R#\ V4P 4pVP 4\9d\VP 4,#\P!\\4;_uu_4\V4\9d \V4MRuuRRR4# +'giR#;i)zMap ``database.synchronous`` (``OFF``/``NORMAL``/``FULL``/``EXTRA`` any case, or ``0``-``3``) to its PRAGMA integer; None for anything else so the caller warns and leaves the level untouched (guessing at durability is worse).FN) r0rWrdr+rrupperr*rGrHrerf)r-texts& rresolve_synchronous_levelr1_s)T""&q0D0)S!!%);;yEE y>   !D zz|**"4::<00   Y 3 3I);;s4y 4 3 3 3 s :!C&& C7 c(V^8dQhRRRRRRRR/#) rr!r"r-rrrrr=r)rs"rrrps+44$6434UX4]a4rc\V4;pf\PRW!4R#\PR8Xd0V\ 8d%\PRV\ V,4R#\P!\P4;_uu_4VPRV 24RRR4R# +'giR#;i)uSet ``PRAGMA synchronous`` from config, never below FULL on macOS. Kept out of the integer loop in :func:`apply_database_pragmas`: this PRAGMA decides whether a commit is on the platter, so an unrecognised value must not fall through to "SQLite default" the way a bad ``cache_size`` can. Darwin floor: this runs after :func:`_enforce_macos_synchronous_full`, so a configured ``NORMAL`` would silently undo the btree protection — raising is allowed, lowering is refused out loud.Nz]%s: ignoring unrecognized database.synchronous=%r (expected OFF, NORMAL, FULL, EXTRA, or 0-3)rDz%s: refusing database.synchronous=%s on macOS; keeping FULL. Darwin's fsync() does not guarantee write ordering, so a lower level readmits the half-written btree pages FULL exists to prevent.zPRAGMA synchronous=) r1r4warningrErF_SYNCHRONOUS_FULLr+rGrHr,r-r*)r!r-rrs&&$ r_apply_synchronous_pragmar6ps+955>v , ||xE,=$=%&.0B50I K    W55 6 6 *5'23 7 6 6 6s B77 C c$V^8dQhRRRRRR/#)rr!r"rrrr=r)rs"rrrs(LL!3L#LW[Lrc "^RIHpHpV!4pR FpT!TRTRR7;pfK\ \ T4P 44p\P!\P4;_uu_4TPRT RT 24RRR4K T!TRRRR7;pe\!YTR 7R#R# \dR#i;i \\3d\PRYT4Ki;i +'giK;i) aTApply optional performance and WAL-sizing PRAGMAs from ``config.yaml``. Journal mode is NOT handled here (owned by :func:`apply_wal_with_fallback`). ``database:`` keys: ``cache_size`` (negative = KiB, positive = pages), ``mmap_size`` (bytes, 0 = off), ``temp_store`` (0-3), ``wal_autocheckpoint`` (pages), ``journal_size_limit`` (bytes), ``synchronous`` (unset leaves the compile-time default, which differs between bundled/distro/Homebrew builds). Best-effort: failures are ignored so DB init never breaks on a malformed section. Applied to ALL connection types: writer, read_only, WAL readers.)cfg_getrjNrk)defaultz'%s: ignoring non-integer database.%s=%rzPRAGMA = synchronousr) cache_size mmap_size temp_storewal_autocheckpointjournal_size_limit)ror9rjrrrdrrrerfr4r4rGrHr,r-r*r6) r!rr9rjcfg pragma_namer-valueraw_synchronouss &$ rapply_database_pragmasrFsC"$m  j+tL LI U  I,,./E !9!9 : : LL7;-q8 9; :m#3 M4PP]!$(K^ :&  NNDh]f g  ; : :s.B<"C7C=< C  C (C:9C:= D )zlocking protocolznot authorizedr&ir>9p9p2000virtiofs9p2000.l9p2000.u fuse.virtiofs)z/proc/self/mountinfo)Y__conditional_annotations__r{ __future__rrG functoolsloggingrr,rE threadingr.typingrrrhermes_cli.sqlite_runtimerrYhermes_state_errorsr getLoggerr4rr?rr __annotations__Lock_wal_fallback_warned_lockr _wal_delete_fallback_failed_lockr _wal_probe_unknown_lockr _wal_reset_bug_warned_lockr _delete_overridden_warned_lockr_journal_upgrade_warned_lockrrr:r@rIrNrQrTrargrtr-rv frozensetrr}rr~_cross_vm_warned_lockr"_cross_vm_existing_wal_warned_lockrrrrrrrrrrrrWARNINGERRORrrrrpartialrrr*itemsr+r5r1r6rF)kvrMs00@rrgs #   &&g4   > *Q((+uH,%NN,/2e!83#,>>#3 &)U(*#..*(+X-&^^-,/E1!*!1%(Us*(~~/8 M 0@! :4*r = 8T'22Tcd&(O(#..*#&5(!(03#X5%.^^%5".M VBVBinVBrIXD*7#gl#L v&!n A 02OQXQ`Q` UV 46UW^WfWf < =.0Lgmm ij !#CEhjqjyjy  H #I8:[]d]j]j XY 13Mw [\ )+CW__ !!CEjlslyly  !_9 x UqTYq I #**9nE)2):):9FY)Z&(-a1faRS&T^T7J7P7P7R%S7Rtqad7R%SNS"4(L LLS&Ts6 L&