cac841d8e6
There are situations where we may be hitting our SQLITE_BUSY timeout when we go to trim. One possibility is that we may have a large ongoing write when we go to trim. So, this change just makes sure we're caught up before we go to trim, which is the simplest thing we can do to address this. It's not a foolproof solution though, so if we still see it crop up, we'll just have to re-route all log operations through the single thread we have setup in the PersistentLogger or something. |
||
|---|---|---|
| .. | ||
| .tx | ||
| jni | ||
| proguard | ||
| sampledata | ||
| src | ||
| build.gradle | ||
| lint-baseline.xml | ||
| lint.xml | ||
| translations.gradle | ||
| witness-verifications.gradle | ||