-
- Downloads
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).
Showing
- changelog.d/14213.misc 1 addition, 0 deletionschangelog.d/14213.misc
- docker/README.md 2 additions, 1 deletiondocker/README.md
- docker/conf/log.config 24 additions, 6 deletionsdocker/conf/log.config
- docker/configure_workers_and_start.py 3 additions, 0 deletionsdocker/configure_workers_and_start.py
- scripts-dev/complement.sh 4 additions, 0 deletionsscripts-dev/complement.sh
- synapse/visibility.py 7 additions, 7 deletionssynapse/visibility.py
- tests/test_utils/logging_setup.py 12 additions, 0 deletionstests/test_utils/logging_setup.py
changelog.d/14213.misc
0 → 100644
Please register or sign in to comment