A failed SQLite integrity check on Windows that reported itself as a POSIX lock conflict

Description and use

A POSIX lock error in YantrikDB on Windows 11 blocked writes, but was fixed in v0.23.2, which now correctly reports quick_check failures and resumes writes after a successful check.

Problem

Hermes Agent writes to a YantrikDB memory store on Windows 11 failed for hours with a POSIX lock conflict error, even though POSIX locks do not exist on Windows.

Outcome

The bug was caused by a mis‑interpreted POSIX lock error on Windows, leading to write failures. The fix in YantrikDB 0.23.2 restores normal operation and improves error reporting.

Workflow

• 1. Hermes Agent attempted to write to YantrikDB on Windows 11.
• 2. YantrikDB reported a POSIX lock conflict error, blocking writes.
• 3. The error was traced to a failed quick_check triggered by an external commit detected by the materializer.
• 4. The issue was reported to the YantrikDB repository with stats() evidence.
• 5. YantrikDB released v0.23.2 with a new IntegrityCheckFailed error, updated stats(), and improved retry logic.
• 6. The agent was upgraded to v0.23.2 and writes resumed automatically after a successful quick_check.

Evidence

"YantrikDB unavailable: remember failed: refusing to write: another SQLite library has C:/Users/<user>/AppData/Local/hermes/yantrikdb-memory-ml.db open in this process"

Source

The engine refusing those writes was YantrikDB 0.23.1, a persistent memory engine for AI agents that I maintain (Rust core, Python bindings on PyPI).

Source

The fix is commit 33d0be9, 15 files changed, +404/-45, released as v0.23.2 (tagged 2026-10-02T07:04:44Z; pip install -U yantrikdb).

Source