-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Internal error due to NUL byte in Conduit federation #10886
Comments
This seems to be caused by this code (where we insert into the synapse/synapse/storage/databases/main/events.py Lines 1640 to 1661 in 94b620a
It's likely a null byte in a display name or avatar URL. (I wonder if it's possible for null bytes to be in the membership value at this point? Would have thought not as presumably that event would be soft-failed and not trigger this code, but I haven't checked that.) It's not entirely clear what the best thing to do is here; it probably depends on where this table is used. It might be acceptable to convert display names/avatar URLs to |
I think we already do this for displaynames/avatar URLs which aren't strings somewhere. +1 to extending that to NUL bytes |
aside: a concern was expressed about storing JSON which contains NULs in the database in general. What we forgot at the time is that, in JSON, NUL bytes within strings are represented as |
This internal error just happened to sbd. when joining #conduit:fachschaften.org (the main Conduit room) with Synapse:
Originally posted by @jplatte in #9341 (comment)
The text was updated successfully, but these errors were encountered: