RomanNum3ral
/
hermes-agent
mirror of https://github.com/NousResearch/hermes-agent.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix(ci): sync lazy_deps SDK pins + update WAL vacuum test contract 

The Aug 12 pin bump (91345435a) updated pyproject/uv.lock but not
tools/lazy_deps.py, tripping the #31817 downgrade-guard tests; the
post-VACUUM TRUNCATE fix landed without updating the checkpoint test
that pinned the old no-TRUNCATE rule. Both red on pristine main.
This commit is contained in:
Teknium 2026-08-12 19:55:50 -07:00
parent 46e20083d8
commit fe8b44dac4
2 changed files with 18 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
tests/test_wal_checkpoint_strategy.py
View File

@ -137,7 +137,16 @@ class TestVacuumUsesPassive:
"""Manual vacuum paths must checkpoint PASSIVE, never TRUNCATE."""
def test_vacuum_uses_passive_before_vacuum(self, db):
"""SessionDB.vacuum() checkpoints PASSIVE before running VACUUM."""
"""SessionDB.vacuum() checkpoints PASSIVE before VACUUM.
A TRUNCATE checkpoint AFTER the VACUUM is expected: VACUUM rewrites
every page through the WAL, so without it a 3 GB database leaves a
3 GB state.db-wal behind and `sessions optimize` becomes a net disk
LOSS. The #45383 tearing concern is about truncating while another
writer is mid-transaction — the pre-VACUUM checkpoint stays PASSIVE
for that reason; the post-VACUUM truncate runs under the same
exclusive-lock window the VACUUM itself required.
"""
real_conn = db._conn
tracking_conn = TrackingConnection(real_conn)
db._conn = tracking_conn
@ -152,12 +161,13 @@ class TestVacuumUsesPassive:
vacuum_calls = [
c for c in tracking_conn.execute_calls if c.strip().upper() == "VACUUM"
]
assert truncate_calls == []
assert passive_calls == ["PRAGMA wal_checkpoint(PASSIVE)"]
assert vacuum_calls == ["VACUUM"]
assert tracking_conn.execute_calls.index(
passive_calls[0]
) < tracking_conn.execute_calls.index(vacuum_calls[0])
assert truncate_calls == ["PRAGMA wal_checkpoint(TRUNCATE)"]
vacuum_index = tracking_conn.execute_calls.index(vacuum_calls[0])
assert tracking_conn.execute_calls.index(passive_calls[0]) < vacuum_index
# TRUNCATE must come only AFTER the VACUUM (never before it).
assert tracking_conn.execute_calls.index(truncate_calls[0]) > vacuum_index
def test_optimize_storage_uses_passive_after_vacuum(self, db):
"""optimize_fts_storage() checkpoints PASSIVE after its VACUUM."""

6
tools/lazy_deps.py
View File

@ -203,7 +203,7 @@ LAZY_DEPS: dict[str, tuple[str, ...]] = {
"memory.mem0": ("mem0ai==2.0.10",),
# ─── Messaging platforms (lazy-installable on demand) ──────────────────
"platform.telegram": ("python-telegram-bot[webhooks]==22.6",),
"platform.telegram": ("python-telegram-bot[webhooks]==22.8",),
# brotlicffi gives aiohttp a working 2-arg Decompressor.process() for
# Discord CDN's Brotli-encoded attachments. Without it, aiohttp falls
# back to google's `Brotli` package (1-arg API), and any .txt/.md/.doc
@ -219,12 +219,12 @@ LAZY_DEPS: dict[str, tuple[str, ...]] = {
"aiohttp==3.14.3", # prior CVEs + GHSA-cq5v-8q36-5273/GHSA-mfx4-hv73-q22v/GHSA-mq44-7p77-q5h7
),
"platform.slack": (
"slack-bolt==1.29.0",
"slack-bolt==1.30.0",
"slack-sdk==3.43.0",
"aiohttp==3.14.3", # prior CVEs + GHSA-cq5v-8q36-5273/GHSA-mfx4-hv73-q22v/GHSA-mq44-7p77-q5h7
),
"platform.matrix": (
"mautrix[encryption]==0.21.0",
"mautrix[encryption]==0.21.1",
"aiosqlite==0.22.1",
"asyncpg==0.31.0",
"aiohttp-socks==0.11.0",