synapse/synapse/federation
Erik Johnston 89a76d1889 Fix handling of redacted events from federation
If we receive an event that doesn't pass their content hash check (e.g.
due to already being redacted) then we hit a bug which causes an
exception to be raised, which then promplty stops the event (and
request) from being processed.

This effects all sorts of federation APIs, including joining rooms with
a redacted state event.
2018-09-13 15:44:12 +01:00
..
transport Port federation/ to py3 (#3847) 2018-09-12 23:23:32 +10:00
__init__.py Remove unused ReplicationLayer 2018-03-13 11:00:04 +00:00
federation_base.py Fix handling of redacted events from federation 2018-09-13 15:44:12 +01:00
federation_client.py Port federation/ to py3 (#3847) 2018-09-12 23:23:32 +10:00
federation_server.py Merge branch 'master' into develop 2018-09-06 13:05:22 +01:00
persistence.py Fix origin handling for pushed transactions 2018-09-05 13:08:07 +01:00
send_queue.py fix #3445 2018-08-29 16:28:25 +02:00
transaction_queue.py Limit the number of PDUs/EDUs per fedreation transaction 2018-09-06 15:23:55 +01:00
units.py Remove pdu_failures from transactions 2018-07-30 16:28:47 -06:00