759828c0f5e81ba0b4939bbe44bc208f18d68fbd
Reads (read/readFrom/lastSequence/allEvents/allSessionIds/lastGlobalSequence) shared the single JDBC Connection with append's transaction unsynchronized. The coroutine appendMutex only excludes append-vs-append; a read on the caller thread could hit the connection mid-transaction (setAutoCommit(false)..commit) and corrupt tx state — SQLite JDBC is not thread-safe. Guard every connection access with a shared JVM monitor (synchronized(connection)) via withConnection, so reads and the IO-thread append transaction are mutually exclusive.
fix: workflow inference chain — surface llama-server errors, user-turn-last, bundle-relative prompts
Description
No description provided
Languages
Kotlin
88.4%
Go
11.4%
Python
0.2%