Bruno Windels 7e8cc7ae00 need to return the response here, not the request wrapper ... we were reading back a remote id of undefined because of this, so when for some reason we never receive the message down from sync, the pending message keeps sending on every load. The server ignores the send though, because the transaction id is already used, and it returns the remote id of the event that was already sent the previous time, but as we were not storing this remote id, we'd just try again and again. not receiving it through sync could have happened when we were sending a bunch of events and then receiving (this is how we encountered this bug, while trying to repro another) the response, but not yet the sync for the message that got wedged. Then we typed stuff on another client so we would get a limited response for that room, and boom, we would not get the remote echo of the event that was already sent (but because of this bug we didn't store the remote id) but no echo received yet (when we remove the pending event), so it gets wedged!		2020-03-17 00:11:50 +01:00
..
net	add record/replay network layer	2019-12-23 14:28:42 +01:00
room	need to return the response here, not the request wrapper	2020-03-17 00:11:50 +01:00
sessions-store/localstorage	add delete button in session picker	2019-10-12 21:16:48 +02:00
storage	add proper import/export functionality	2019-12-14 18:29:35 +01:00
error.js	fix errors when replaying	2020-03-17 00:07:54 +01:00
hs-api.js	fix errors when replaying	2020-03-17 00:07:54 +01:00
SendScheduler.js	fixup: delay not awaited, but not needed for now	2019-07-29 19:53:30 +02:00
session.js	fix all tests	2020-03-14 21:38:37 +01:00
sync.js	only apply sync changes in room summary once txn is committed	2020-03-14 20:46:49 +01:00
User.js	return syncing user id from PendingEventEntry.sender	2019-07-29 10:24:34 +02:00