diff options
author | Patrick Cloke <clokep@users.noreply.github.com> | 2022-04-12 11:27:45 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-04-12 11:27:45 -0400 |
commit | 4bdbebccb98bcc0e8862b1e8b532d9a491a90dac (patch) | |
tree | 380b571462a5414b3032cbd623c9e09a904a27d2 /synapse/federation/transport | |
parent | Fix typos in release script docs (#12450) (diff) | |
download | synapse-4bdbebccb98bcc0e8862b1e8b532d9a491a90dac.tar.xz |
Remove the unstable event field for `/send_join` per MSC3083. (#12395)
This was missed when initially stabilising room version 8 and was left in as a compatibility shim. Most homeservers have upgraded to a version which expects the proper field name, and the failure mode is reasonable (a user on an older server may have to attempt joining the room twice with an obscure error message the first time).
Diffstat (limited to 'synapse/federation/transport')
-rw-r--r-- | synapse/federation/transport/client.py | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/synapse/federation/transport/client.py b/synapse/federation/transport/client.py index 01dc5ca94f..1421050b9a 100644 --- a/synapse/federation/transport/client.py +++ b/synapse/federation/transport/client.py @@ -1380,16 +1380,6 @@ class SendJoinParser(ByteParser[SendJoinResponse]): prefix + "auth_chain.item", use_float=True, ), - # TODO Remove the unstable prefix when servers have updated. - # - # By re-using the same event dictionary this will cause the parsing of - # org.matrix.msc3083.v2.event and event to stomp over each other. - # Generally this should be fine. - ijson.kvitems_coro( - _event_parser(self._response.event_dict), - prefix + "org.matrix.msc3083.v2.event", - use_float=True, - ), ijson.kvitems_coro( _event_parser(self._response.event_dict), prefix + "event", |