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
When using a sqlite3 database, rebooting Synapse may cause it to reset its transaction ID count, meaning the IDs of future transactions will start from 1. This means existing appservices which use the transaction ID to deduplicate events may consider new transactions as ones they've seen before, until Synapse's transaction ID catches up to the most recent transaction ID that the appservice actually handled.
Steps to reproduce
connect some appservices to Synapse
boot Synapse & the appservices and run them for a while
reboot Synapse
watch Synapse & appservice logs to see transaction IDs start at 1 after the reboot
My usecase for sqlite3 is to have a set of easily resettable Synapse databases for quick local testing. Having transaction IDs reset every so often gets in the way of testing Synapse with appservices, as it renders them mostly unusable until Synapse's transaction IDs catch up.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #14556.
Description
When using a sqlite3 database, rebooting Synapse may cause it to reset its transaction ID count, meaning the IDs of future transactions will start from 1. This means existing appservices which use the transaction ID to deduplicate events may consider new transactions as ones they've seen before, until Synapse's transaction ID catches up to the most recent transaction ID that the appservice actually handled.
Steps to reproduce
Homeserver
Local testing homeserver
Synapse Version
v1.69.0
Installation Method
Other (please mention below)
Database
SQLite
Workers
Single process
Platform
Fedora Linux 37 (Workstation Edition), 64-bit
Configuration
Some experimental features:
Relevant log output
Anything else that would be useful to know?
last_txn
AS state matrix-org/synapse#12209.The text was updated successfully, but these errors were encountered: