diff options
| author | Travis Ralston <travpc@gmail.com> | 2019-05-22 19:14:10 -0600 |
|---|---|---|
| committer | Travis Ralston <travpc@gmail.com> | 2019-05-22 19:14:10 -0600 |
| commit | f9d7d3aa89f80da29736b35ab81d55dd5ea2d384 (patch) | |
| tree | f48e41151defdf92c949d72eea0e17fd78603401 /tests/storage/test_presence.py | |
| parent | Run black on synapse.crypto.keyring (#5232) (diff) | |
| download | synapse-f9d7d3aa89f80da29736b35ab81d55dd5ea2d384.tar.xz | |
Remove m.relates_to from events if the client set it to null
It appears as though Python only checks to see if the key exists in a dictionary, not necessarily for a useful value. This means that when clients submit (valid) requests with `m.relates_to: null` and Synapse later reads it, it gets a None reference error on access. This is the easier route than guarding all the places where it could be None.
Diffstat (limited to 'tests/storage/test_presence.py')
0 files changed, 0 insertions, 0 deletions