Eric Eastwood 70a4317692 Track when the pulled event signature fails (#13815) ... Because we're doing the recording in `_check_sigs_and_hash_for_pulled_events_and_fetch` (previously named `_check_sigs_and_hash_and_fetch`), this means we will track signature failures for `backfill`, `get_room_state`, `get_event_auth`, and `get_missing_events` (all pulled event scenarios). And we also record signature failures from `get_pdu`. Part of https://github.com/matrix-org/synapse/issues/13700 Part of https://github.com/matrix-org/synapse/issues/13676 and https://github.com/matrix-org/synapse/issues/13356 This PR will be especially important for https://github.com/matrix-org/synapse/pull/13816 so we can avoid the costly `_get_state_ids_after_missing_prev_event` down the line when `/messages` calls backfill.		2022-10-03 14:53:29 -05:00
..
sender	…
transport	…
__init__.py	…
federation_base.py	Track when the pulled event signature fails (#13815)	2022-10-03 14:53:29 -05:00
federation_client.py	Track when the pulled event signature fails (#13815)	2022-10-03 14:53:29 -05:00
federation_server.py	…
persistence.py	…
send_queue.py	…
units.py	…