Allow mocking timers in tests - #33
Merged
Merged
Conversation
simolus3
commented
Sep 15, 2026
Chriztiaan
approved these changes
Sep 15, 2026
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.
This refactors the sync retry delay to be based on sync options passed to the upload / download actors (instead of a field on the database). This is mostly a preparation for checkpoint requests: The current test timer implementation panics (and we carefully set a zero duration on existing tests with failures), but that won't work for the intentional checkpoint retry loop. So, this adds a simple mocked timer implementation we can forward manually.
As another small fix, this applies the cache size and busy timeout pragma on all connections instead of just on the writer. Closes #28.
AI use: Reviewed with Claude Code.