| 13 Nov 2025 |
 lillecarl | I just update the time, never remove anything. But actually looking at it again. Why is there no RETRY_SQLITE around https://git.lix.systems/lix-project/lix/src/branch/main/lix/libstore/local-store.cc#L780 like all other query functions in this class? 🤔 | 12:21:39 |
 raitobezarius | because it's probably up to the caller to do the retry and there might be some optimistic querying happening here? | 12:22:08 |
| lillecarl | Possibly, but moving my own query to execute after rather than before whatever the daemon op was doing worked. I'll check the paths that call queryValidPathId | 12:24:43 |
| lillecarl | * Possibly, but moving my own query to execute after rather than before whatever the daemon op was doing worked. I'll check the paths that call queryValidPathId
Edit: Yep all of them are from within retry SQLite lambdas | 12:25:23 |
| lillecarl | I believe there's something lurking here, while I'm doing updates in "query code" I don't see how running update before a select could trigger this | 12:27:35 |
| lillecarl | I've never touched async C++ before fiddling with Lix though but my intuition says I'm not doing something overly wrong, unsupported for sure but not "database is corrupt" wrong | 12:29:29 |
| lillecarl | I didn't open an immediate txn 💡 | 12:36:53 |
