-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synapse has accepted a power levels event with a malformed notifications
field into current state
#14349
Comments
Or maybe it's related to room state, since upgrade gives also a funny result: {"new_version":"10"} and the server response was {"errcode":"M_BAD_JSON","error":"\"notifications\": 150 is not of type 'object'"} |
What is the content of the current power levels event in that room (as seen by your server)? |
Reminds me a bit of #14060. |
The following DB query will answer this: SELECT json
FROM current_state_events cse
JOIN event_json USING(event_id)
WHERE cse.room_id = '!YcwkOsrOwEmdsTNhLw:grin.hu' AND cse.type = 'm.room.power_levels' AND cse.state_key = ''
; Alternatively you could make a |
{ "ban":800,
"events":
{"im.vector.modular.widgets":400, "m.room.avatar":400, "m.room.canonical_alias":400,
"m.room.history_visibility":400, "m.room.name":500, "m.room.power_levels":900,
"m.room.topic":400},
"events_default":10, "invite":50, "kick":700, "notifications":150, "redact":25, "state_default":400,
"users": {"xxx": 1000000} ,
"users_default":100} Oh. I see that's a non-synapse created room. |
No, the reason is that
To fix this: change the state of the room so that the power levels has
Might be worth filing a bug against whichever server created the room (edit: and/or whichever client set those power levels): that's an invalid power levels event. Equally: Synapse should have rejected that power levels event when it joined the room, so we have a bug of our own. |
notifications
field into current state
Before room v10 we allowed a sloppier I'm not 100% convinced this was legit under old rooms, but if it was we shouldn't internally error like this. |
Description
Got this:
Steps to reproduce
This was a response to a m.room.message, which may have been misformatted?
Homeserver
grin.hu
Synapse Version
1.69.0
Installation Method
Other (please mention below)
Platform
Debian package from debian.
OS: Debian/bookworm (and some sid due to deps), amd64.
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: