kegsay 6de29c1cd2 bugfix: E2EE device keys could sometimes not be sent to remote servers (#2466) ... * Fix flakey sytest 'Local device key changes get to remote servers' * Debug logs * Remove internal/test and use /test only Remove a lot of ancient code too. * Use FederationRoomserverAPI in more places * Use more interfaces in federationapi; begin adding regression test * Linting * Add regression test * Unbreak tests * ALL THE LOGS * Fix a race condition which could cause events to not be sent to servers If a new room event which rewrites state arrives, we remove all joined hosts then re-calculate them. This wasn't done in a transaction so for a brief period we would have no joined hosts. During this interim, key change events which arrive would not be sent to destination servers. This would sporadically fail on sytest. * Unbreak new tests * Linting		2022-05-17 13:23:35 +01:00
..
postgres	Add indexes to syncapi_output_room_events table that satisfy the filters (#2446)	2022-05-10 11:23:36 +01:00
shared	Only load members of newly joined rooms (#2389)	2022-04-28 18:53:28 +02:00
sqlite3	Add indexes to syncapi_output_room_events table that satisfy the filters (#2446)	2022-05-10 11:23:36 +01:00
tables	bugfix: E2EE device keys could sometimes not be sent to remote servers (#2466)	2022-05-17 13:23:35 +01:00
interface.go	Only load members of newly joined rooms (#2389)	2022-04-28 18:53:28 +02:00
storage.go	Global database connection pool (for monolith mode) (#2411)	2022-05-03 16:35:06 +01:00
storage_test.go	bugfix: E2EE device keys could sometimes not be sent to remote servers (#2466)	2022-05-17 13:23:35 +01:00
storage_wasm.go	Global database connection pool (for monolith mode) (#2411)	2022-05-03 16:35:06 +01:00