You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tactic is to upgrade the SQLite version in order to support the RETURNING keyword. This would allow not to use a transaction.
Update the Signer & Aggregator documentation + SPO guide to inform about SQLite minimum version (3.35)
Remove the useless harness test in SQLiteAdapter
Issue
We have noticed some database locks occurring on the GCP Aggregator which these error messages:
cannot start a transaction within a transaction
database is locked
⚠ The problem occurred after activating the
pruning
feature of the stores #516Here are the full logs:
Workaround
Restart the container
The text was updated successfully, but these errors were encountered: