We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated to GRDB from 4.9.0 to 4.12.0.
No deadlock.
A deadlock occurred during migration.
GRDB flavor(s): GRDB GRDB version: 4.12.0 Installation method: SPM Xcode version: 11.4 Swift version: 5.2 Platform(s) running GRDB: iOS 13.4 macOS version running Xcode: 10.15.4
Assign a target queue to the configuration
var configuration = Configuration() configuration.targetQueue = targetQueue
Enable erase database on schema change
var migrator = DatabaseMigrator() migrator.eraseDatabaseOnSchemaChange = true
A deadlock will occur at line 51 of SerializedDatabase.swift after calling migrator.migrate. try queue.sync {
migrator.migrate
try queue.sync {
4.10.0 doesn't have this issue. 4.11.0 does.
The text was updated successfully, but these errors were encountered:
Hello @cosmer-work, thank you for the report!
Sorry, something went wrong.
Failing test for #741
70c6f3e
Fix failing test for #741
97a84c6
A fix has been pushed in v4.12.1
Thank you @groue.
No branches or pull requests
What did you do?
Updated to GRDB from 4.9.0 to 4.12.0.
What did you expect to happen?
No deadlock.
What happened instead?
A deadlock occurred during migration.
Environment
GRDB flavor(s): GRDB
GRDB version: 4.12.0
Installation method: SPM
Xcode version: 11.4
Swift version: 5.2
Platform(s) running GRDB: iOS 13.4
macOS version running Xcode: 10.15.4
Steps to Reproduce
Assign a target queue to the configuration
Enable erase database on schema change
A deadlock will occur at line 51 of SerializedDatabase.swift after calling
migrator.migrate.try queue.sync {4.10.0 doesn't have this issue. 4.11.0 does.
The text was updated successfully, but these errors were encountered: