summary refs log tree commit diff
path: root/Cargo.lock
diff options
context:
space:
mode:
authorEric Eastwood <erice@element.io>2023-06-01 21:27:18 -0500
committerGitHub <noreply@github.com>2023-06-01 21:27:18 -0500
commit30a5076da8ad776c150ad2745b5f34b4446012e0 (patch)
treef2545745ea46c209767f94d157a4e9b6ee539e03 /Cargo.lock
parentMerge branch 'release-v1.85' into develop (diff)
downloadsynapse-30a5076da8ad776c150ad2745b5f34b4446012e0.tar.xz
Log when events are (unexpectedly) filtered out of responses in tests (#14213)
See https://github.com/matrix-org/synapse/pull/14095#discussion_r990335492

This is useful because when see that a relevant event is an `outlier` or `soft-failed`, then that's a good unexpected indicator explaining why it's not showing up. `filter_events_for_client` is used in `/sync`, `/messages`, `/context` which are all common end-to-end assertion touch points (also notifications, relations).
Diffstat (limited to 'Cargo.lock')
0 files changed, 0 insertions, 0 deletions