fix(tui_gateway): stop the bot mailbox poll from flooding the log on installs that never received a delivery
The per-session notification poller ran `_poll_bot_live_delivery_once` every 0.5 s. Once a "Bot Chat" session exists, each pass opens state.db and takes the exclusive active-session registry lock; on Windows (`msvcrt` LK_LOCK gives up after 10 s of contention) that raised `RuntimeError: active session file lock unavailable` and the loop logged `Bot live-owner delivery poll failed` on every attempt — 8,838 warnings in three days, 91% of one install's WARNING output (#111719). Two changes: - `tools/bot_live_delivery.has_mailbox`: the mailbox directory is created only when a delivery is first admitted, so a profile without it has nothing to claim — the poll now returns before the state.db open / registry lock. This keeps cron→Bot Chat and Bot Mode DM delivery intact on installs with no messaging platform configured (both deliver through this mailbox), which is why the poll is gated on the mailbox rather than on connected platforms (PR #111733's guard would have broken those). - `_poll_bot_live_delivery_guarded`: a failing poll backs off 5 s before the next attempt and is logged at WARNING once per 60 s window (with the count of suppressed repeats), DEBUG otherwise. Live probe (real poller loop, temp HERMES_HOME with a Bot Chat row and the registry lock made unavailable, 3 s): before: owner_lookups=6 WARNING=6 (with or without a mailbox) after: no mailbox -> owner_lookups=0 WARNING=0; mailbox -> owner_lookups=1 WARNING=1 Fixes #111719 Co-authored-by: KoNit-K <124019182+KoNit-K@users.noreply.github.com>
This commit is contained in:
@@ -76,6 +76,13 @@ def _root(home: Path | str) -> Path:
|
||||
return Path(home).resolve() / "runtime" / DELIVERY_DIR_NAME
|
||||
|
||||
|
||||
def has_mailbox(profile_home: Path | str) -> bool:
|
||||
"""Whether any delivery was ever admitted for this profile (the mailbox directory is created on
|
||||
first admission only). A cheap pre-check for pollers: no mailbox means nothing to claim, so the
|
||||
owner lookup — a state.db open plus the exclusive active-session registry lock — can be skipped."""
|
||||
return _root(profile_home).is_dir()
|
||||
|
||||
|
||||
@contextmanager
|
||||
def _locked(home: Path | str):
|
||||
root = _root(home)
|
||||
|
||||
Reference in New Issue
Block a user