30a5076da8
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). |
||
---|---|---|
.. | ||
build_debian_packages.py | ||
check-newsfragment.sh | ||
check_line_terminators.sh | ||
check_locked_deps_have_sdists.py | ||
check_pydantic_models.py | ||
check_schema_delta.py | ||
complement.sh | ||
config-lint.sh | ||
database-save.sh | ||
docker_update_debian_changelog.sh | ||
dump_macaroon.py | ||
federation_client.py | ||
generate_sample_config.sh | ||
lint.sh | ||
make_full_schema.sh | ||
mypy_synapse_plugin.py | ||
next_github_number.sh | ||
release.py | ||
sign_json.py |