߲jg dZddlmZddlZddlZddlZddlmZddlm Z m Z ddddejdd dd  dd Z ejdd dd ZddZejddZy)uShared SQLite primitives for the small per-profile / board stores. ``open_db`` is the one connect + PRAGMA stack; ``transaction`` is the one commit-and-ALWAYS-close shape. Every hand-rolled ``_connect``/``_transaction`` pair used to re-carry the #69567 fix (a ``with conn:`` only commits — it never closes, so each call leaked a connection and its WAL/SHM fds until GC, exhausting ``RLIMIT_NOFILE`` on long-running gateways) and at least one copy missed it. ) annotationsN)Path)CallableIteratoriTF)busy_timeout_mswal foreign_keyssynchronous_full row_factorycheck_same_threadwal_lock_retries initializec zddlm} t|}|jj ddt j ||dz |} || _| jdt||rt|D]} | | |n|r| jd|r| jd| | | | S#t j$rJ} t| jd k7s| d z|k(rtjd d | zzYd } ~ d } ~ wwxYw#t $r| j#wxYw)uOpen ``path`` (parent created), apply the PRAGMA set, run ``initialize``; closed if anything raises. ``busy_timeout_ms`` is the single busy knob: it is passed as ``connect(timeout=)`` AND set as the explicit PRAGMA so it is observable. ``wal=True`` goes through ``apply_wal_with_fallback`` — the only journal-mode setter that carries the WAL-reset-bug gate, the network-FS silent-refusal fallback and the never-live-downgrade invariant; a raw ``PRAGMA journal_mode=WAL`` bypasses all three. Only the transient ``database is locked`` from that pragma is retried (``wal_lock_retries``): a first opener initializing a shared DB can make it ignore the busy timeout, notably on Windows. r)apply_wal_with_fallbackT)parentsexist_oki)timeoutr zPRAGMA busy_timeout=)db_labelzdatabase is lockedrg{Gz?NzPRAGMA foreign_keys=ONzPRAGMA synchronous=FULL)hermes_state_walrrparentmkdirsqlite3connectr executeintrangeOperationalErrorstrlowertimesleep BaseExceptionclose)pathrrr r r r r rrrconnattemptexcs ;/home/ubuntu/.hermes/hermes-agent/hermes_cli/sqlite_util.pyopen_dbr+s6,9 :DKKdT2 ??44)?Sd eD& +C,@+ABC  !12 44+D8D 4  LL1 2  LL2 3  ! t  K//43x~~'+??7Q;RbCbJJtq'z2334   s7 4D B? 3D?DADDDDD:) immediatec#K |r|jd|5|ddd|jy#1swYxYw#|jwxYww)z\Commit on success, roll back on error, and ALWAYS close ``conn`` (see the module docstring).BEGIN IMMEDIATEN)rr%)r'r,s r* transactionr/FsN  LL* +  J     s.AA7AAAAAAc |jd|d|y#tj$r&}dt|j vrYd}~yd}~wwxYw)a#``ALTER TABLE ADD COLUMN ``, idempotent across races: True when this call added it, False on the ``duplicate column name`` a concurrent migrator caused. ``column`` is the human-readable name for the call site; ``ddl`` carries the actual definition. See #21708. z ALTER TABLE z ADD COLUMN Tzduplicate column nameNF)rrrr r!)r'tablecolumnddlr)s r*add_column_if_missingr4RsR |E7,se<=  # # "c#hnn&6 6 sAA AAc#K|jd ||jdy#t$r- |jd#tj$rYwxYwwxYww)zAn IMMEDIATE write transaction on a long-lived connection (stays open). The explicit ROLLBACK is guarded so a SQLite auto-rollback (no transaction left under EIO / contention / corruption) cannot shadow the original error.r.COMMITROLLBACKN)r Exceptionrr)r's r* write_txnr9bsp  LL"#   X   LL $ ''    s<A$+A$ A!AA!AA!AA!!A$)r&z Path | strrr rrr boolr r:r r:r r:rrrz+Callable[[sqlite3.Connection], None] | Nonereturnsqlite3.Connection)r'r<r,r:r;zIterator[sqlite3.Connection]) r'r<r1r r2r r3r r;r:)r'r<)__doc__ __future__r contextlibrr"pathlibrtypingrrRowr+contextmanagerr/r4r9r*rFs# % " ">B1 11 1  1  1111<11h ?D   rE