mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-16 19:36:54 +00:00
Change-detectors, tautologies, source-reading tests, redundant duplicates, mock-echo tests and dead/unrunnable tests. Per-test rationale in the lane ledger (category + reason for every removal).
264 lines
9.6 KiB
Python
264 lines
9.6 KiB
Python
"""Regression tests for #31501 — prune stale Telegram DM topic bindings.
|
|
|
|
When a Telegram user deletes a DM topic in the client, the Bot API
|
|
responds to the gateway's next send with ``Thread not found``. The
|
|
adapter falls back to a plain send (no ``message_thread_id``), but
|
|
prior to this fix it left the corresponding row in
|
|
``telegram_dm_topic_bindings`` untouched.
|
|
``gateway.run._recover_telegram_topic_thread_id`` then walked the
|
|
user's bindings newest-first on every later inbound message and
|
|
cheerfully redirected them back to the deleted topic — tool
|
|
progress, approvals and replies all silently landed in the wrong
|
|
place until the operator manually ran ``DELETE`` on ``state.db``.
|
|
|
|
The fix has three pieces — these tests pin the first two plus the
|
|
end-to-end recovery outcome:
|
|
|
|
1. ``SessionDB.delete_telegram_topic_binding`` — the targeted
|
|
prune helper (new public API).
|
|
2. ``TelegramAdapter._prune_stale_dm_topic_binding`` — the
|
|
adapter glue that calls the helper from a send-fallback hot
|
|
path without raising on cleanup failure.
|
|
3. The two "Thread not found" call sites in the streaming send
|
|
loop and the control-message helper now invoke (2).
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from types import SimpleNamespace
|
|
|
|
|
|
from hermes_state import SessionDB
|
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# SessionDB.delete_telegram_topic_binding
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
def _seed_binding(
|
|
db: SessionDB,
|
|
*,
|
|
chat_id: str = "5595856929",
|
|
thread_id: str = "15287",
|
|
user_id: str = "5595856929",
|
|
session_id: str = "sess-target",
|
|
) -> None:
|
|
db.create_session(
|
|
session_id=session_id,
|
|
source="telegram",
|
|
user_id=user_id,
|
|
)
|
|
db.bind_telegram_topic(
|
|
chat_id=chat_id,
|
|
thread_id=thread_id,
|
|
user_id=user_id,
|
|
session_key=f"agent:main:telegram:dm:{chat_id}:{thread_id}",
|
|
session_id=session_id,
|
|
)
|
|
|
|
|
|
class TestDeleteTelegramTopicBinding:
|
|
def test_removes_matching_row_and_returns_count(self, tmp_path):
|
|
db = SessionDB(db_path=tmp_path / "state.db")
|
|
_seed_binding(db, thread_id="15287")
|
|
# Sanity check — binding present before prune.
|
|
assert db.get_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
) is not None
|
|
|
|
removed = db.delete_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
)
|
|
|
|
assert removed == 1
|
|
assert db.get_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
) is None
|
|
db.close()
|
|
|
|
def test_does_not_touch_unrelated_bindings(self, tmp_path):
|
|
# Critical for the fix: a chat with multiple topics must
|
|
# only lose the one Telegram confirmed deleted, never the
|
|
# rest. Otherwise the user's healthy topics also vanish
|
|
# from recovery's view.
|
|
db = SessionDB(db_path=tmp_path / "state.db")
|
|
_seed_binding(db, thread_id="15287", session_id="sess-stale")
|
|
_seed_binding(db, thread_id="15418", session_id="sess-fresh")
|
|
|
|
removed = db.delete_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
)
|
|
assert removed == 1
|
|
|
|
# Stale binding is gone; the fresh one survives.
|
|
assert db.get_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
) is None
|
|
assert db.get_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15418",
|
|
) is not None
|
|
db.close()
|
|
|
|
|
|
class TestPruneClearsTopicModeWhenLastBindingGone:
|
|
"""Proactive cleanup (#31501 follow-up): pruning the chat's final
|
|
binding must also flip ``telegram_dm_topic_mode.enabled`` to 0 so
|
|
recovery fully stands down — covers the user who disabled topics in
|
|
the Telegram client without ever running ``/topic off``."""
|
|
|
|
def test_clears_enabled_when_last_binding_pruned(self, tmp_path):
|
|
db = SessionDB(db_path=tmp_path / "state.db")
|
|
db.enable_telegram_topic_mode(
|
|
chat_id="5595856929", user_id="5595856929",
|
|
)
|
|
_seed_binding(db, thread_id="15287")
|
|
assert db.is_telegram_topic_mode_enabled(
|
|
chat_id="5595856929", user_id="5595856929",
|
|
) is True
|
|
|
|
removed = db.delete_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
)
|
|
|
|
assert removed == 1
|
|
assert db.is_telegram_topic_mode_enabled(
|
|
chat_id="5595856929", user_id="5595856929",
|
|
) is False
|
|
db.close()
|
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Adapter glue — _prune_stale_dm_topic_binding
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
def _bare_adapter(db: SessionDB | None = None):
|
|
# The adapter accesses the SessionDB via
|
|
# ``self._session_store._db`` (set by GatewayRunner via
|
|
# ``set_session_store``). Build a minimal stand-in with just
|
|
# the surface the prune helper touches; we don't need the
|
|
# python-telegram-bot import-graph here. ``name`` is a
|
|
# property that delegates to ``platform.value.title()``, so
|
|
# we set ``platform`` rather than poking ``name`` directly.
|
|
from gateway.config import Platform
|
|
from plugins.platforms.telegram.adapter import TelegramAdapter
|
|
|
|
adapter = object.__new__(TelegramAdapter)
|
|
adapter.platform = Platform.TELEGRAM
|
|
if db is not None:
|
|
adapter._session_store = SimpleNamespace(_db=db)
|
|
return adapter
|
|
|
|
|
|
class TestPruneStaleDmTopicBindingHelper:
|
|
def test_drops_binding_when_session_store_db_is_present(self, tmp_path):
|
|
db = SessionDB(db_path=tmp_path / "state.db")
|
|
_seed_binding(db, thread_id="15287")
|
|
|
|
adapter = _bare_adapter(db)
|
|
adapter._prune_stale_dm_topic_binding("5595856929", 15287)
|
|
|
|
assert db.get_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="15287",
|
|
) is None
|
|
db.close()
|
|
|
|
|
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Source-level wiring guards — both fallback sites must call the helper
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# End-to-end semantic — prune + recovery returns None for deleted topic
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
class TestRecoveryAfterPrune:
|
|
"""The whole point of the fix: once a topic is pruned, the
|
|
GatewayRunner's ``_recover_telegram_topic_thread_id`` must no
|
|
longer steer future inbound messages to it.
|
|
"""
|
|
|
|
def test_recovery_no_longer_returns_pruned_topic(self, tmp_path):
|
|
# Build the same fixture used elsewhere: two topic bindings
|
|
# for the same user, then prune the most-recent one.
|
|
# ``_recover_telegram_topic_thread_id`` walks bindings
|
|
# newest-first, so without the prune it would pick the
|
|
# one we just removed.
|
|
from gateway.config import GatewayConfig, Platform, PlatformConfig
|
|
from gateway.run import GatewayRunner
|
|
from gateway.session import SessionSource, build_session_key
|
|
|
|
db = SessionDB(db_path=tmp_path / "state.db")
|
|
db.enable_telegram_topic_mode(
|
|
chat_id="5595856929", user_id="5595856929",
|
|
)
|
|
|
|
for sid, thread in (("sess-A", "111"), ("sess-B", "222")):
|
|
db.create_session(
|
|
session_id=sid, source="telegram",
|
|
user_id="5595856929",
|
|
)
|
|
db.bind_telegram_topic(
|
|
chat_id="5595856929",
|
|
thread_id=thread,
|
|
user_id="5595856929",
|
|
session_key=build_session_key(SessionSource(
|
|
platform=Platform.TELEGRAM,
|
|
user_id="5595856929",
|
|
chat_id="5595856929",
|
|
user_name="tester",
|
|
chat_type="dm",
|
|
thread_id=thread,
|
|
)),
|
|
session_id=sid,
|
|
)
|
|
|
|
runner = object.__new__(GatewayRunner)
|
|
runner.config = GatewayConfig(
|
|
platforms={
|
|
Platform.TELEGRAM: PlatformConfig(enabled=True, token="***"),
|
|
}
|
|
)
|
|
runner._session_db = db
|
|
runner._telegram_topic_mode_enabled = lambda _src: True
|
|
|
|
# Sanity: before the prune, recovery picks "222" (newest).
|
|
# Recovery only fires for a lobby-shaped inbound (omitted
|
|
# message_thread_id or General topic "1"); a non-lobby
|
|
# unknown thread is preserved as a brand-new topic. Use the
|
|
# General topic id so the recovery walk actually runs.
|
|
before = runner._recover_telegram_topic_thread_id(SessionSource(
|
|
platform=Platform.TELEGRAM,
|
|
user_id="5595856929",
|
|
chat_id="5595856929",
|
|
user_name="tester",
|
|
chat_type="dm",
|
|
thread_id="1", # General/stripped reply — triggers recovery
|
|
))
|
|
assert before == "222"
|
|
|
|
# User deletes topic 222 in Telegram → adapter prunes.
|
|
db.delete_telegram_topic_binding(
|
|
chat_id="5595856929", thread_id="222",
|
|
)
|
|
|
|
# Now recovery falls back to topic 111 (the surviving
|
|
# binding) instead of the dead one. This is the exact
|
|
# behaviour change the bug report asks for.
|
|
after = runner._recover_telegram_topic_thread_id(SessionSource(
|
|
platform=Platform.TELEGRAM,
|
|
user_id="5595856929",
|
|
chat_id="5595856929",
|
|
user_name="tester",
|
|
chat_type="dm",
|
|
thread_id="1",
|
|
))
|
|
assert after == "111"
|
|
db.close()
|