Refactor sync code to use an async transaction/separate looper thread#529
Merged
octoshrimpy merged 1 commit intoquik-sms:masterfrom Aug 29, 2025
Merged
Refactor sync code to use an async transaction/separate looper thread#529octoshrimpy merged 1 commit intoquik-sms:masterfrom
octoshrimpy merged 1 commit intoquik-sms:masterfrom
Conversation
This makes the sync more robust when handling larger message db, as well gives speed improvements.
Closed
This was referenced Nov 13, 2025
Merged
Closed
Merged
This was referenced Dec 9, 2025
Closed
Merged
Merged
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am guessing that on large message db, sync could be unreliable hence the issue in #520. This speeds up the sync process, and makes it more robust
Closes #520