diff options
author | David Robertson <davidr@element.io> | 2023-01-30 21:29:30 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-01-30 21:29:30 +0000 |
commit | 510d4b06e7d346b4f94cb5598da90c9f668b62bb (patch) | |
tree | a8e39c1fe3e43f6dd8329f2df4d48e83416d46f9 /changelog.d | |
parent | Bump types-pillow from 9.4.0.3 to 9.4.0.5 (#14938) (diff) | |
download | synapse-510d4b06e7d346b4f94cb5598da90c9f668b62bb.tar.xz |
Handle malformed values of `notification.room` in power level events (#14942)
* Better test for bad values in power levels events The previous test only checked that Synapse didn't raise an exception, but didn't check that we had correctly interpreted the value of the dodgy power level. It also conflated two things: bad room notification levels, and bad user levels. There _is_ logic for converting the latter to integers, but we should test it separately. * Check we ignore types that don't convert to int * Handle `None` values in `notifications.room` * Changelog * Also test that bad values are rejected by event auth * Docstring * linter scripttttttttt
Diffstat (limited to 'changelog.d')
-rw-r--r-- | changelog.d/14942.bugfix | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/changelog.d/14942.bugfix b/changelog.d/14942.bugfix new file mode 100644 index 0000000000..a3ca3eb7e9 --- /dev/null +++ b/changelog.d/14942.bugfix @@ -0,0 +1 @@ +Fix a bug introduced in Synapse 1.68.0 where we were unable to service remote joins in rooms with `@room` notification levels set to `null` in their (malformed) power levels. |