mirror of
https://github.com/openclaw/openclaw.git
synced 2026-09-28 14:12:28 +08:00
Worker-backed state writes leave a worker holding an idle state-database connection. The synchronous closeOpenClawStateDatabaseForTest() only starts that worker's retirement, whose last-connection checkpoint and WAL delete then land at an arbitrary later time. Fixtures that opened the same database raw or snapshotted/copied its files right after could hit SQLITE_BUSY or see bytes change underneath them. Await closeOpenClawStateDatabaseAsync() at every site a Testbox custody probe showed exposed (same database, live worker custody), make seedLegacyV15ProposalRows() async for the same reason, pin the owner contract in the database-worker WAL test, and document the rule for fixture authors.