Don't startImmediately in tests
#375
Open
Conversation
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
stephencelis
commented
Jan 15, 2026
| try T | ||
| await withErrorReporting(.sqliteDataCloudKitFailure) { | ||
| // NB: Fake 'sending' result. | ||
| nonisolated(unsafe) var result: T.QueryOutput? |
Member
Author
There was a problem hiding this comment.
We can remove this in the future if/when GRDB adopts sending.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Parallelized tests that all start sync engines can lead to database contention/locking, so let's require explicit
await syncEngine.start()to force tests/suites to wait for the sync engine to finish starting before interacting with the database from feature code.