This repository has been archived on 2022-08-19. You can view files and clone it, but cannot push or open issues or pull requests.

Bruno Windels 224d56698a only set new live key when creating a fragment after the txn succeeds ... when doing a limited sync, and a new fragment is created, this._lastLiveKey is updated immediately. If the transaction would then fail, the fragmentId in this._lastLiveKey was incremented but the fragment wasn't written to the store, so if sync is resumed and would subsequently succeed, fragmentIds would be assigned to events that don't have a corresponding fragment in the timelineFragment store. This would throw errors when trying to load the timeline, breaking the whole app. This changes SyncWriter to only update this._lastLiveKey in the emit phase, when the transactions has been committed already.		2020-01-04 20:06:49 +01:00
..
sending	moar send logging	2019-09-15 12:25:14 +02:00
timeline	only set new live key when creating a fragment after the txn succeeds	2020-01-04 20:06:49 +01:00
room.js	only set new live key when creating a fragment after the txn succeeds	2020-01-04 20:06:49 +01:00
summary.js	make sure aliases and heroes aren't empty when picking name	2019-11-22 09:29:18 +01:00