diff options
author | Patrick Cloke <clokep@users.noreply.github.com> | 2023-10-06 07:27:35 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-10-06 07:27:35 -0400 |
commit | fc31b495b3a7f170019591c2e40e699b61c067a1 (patch) | |
tree | 5ce86bdde4e854831a93c3042b75ad7d2a7d8d08 /synapse/federation/transport | |
parent | Fix comments related to replication. (#16428) (diff) | |
download | synapse-fc31b495b3a7f170019591c2e40e699b61c067a1.tar.xz |
Stop sending incorrect knock_state_events. (#16403)
Synapse was incorrectly implemented with a knock_state_events property on some APIs (instead of knock_room_state). This was correct in Synapse 1.70.0, but *both* fields were sent to also be compatible with Synapse versions expecting the wrong field. Enough time has passed that only the correct field needs to be included/handled.
Diffstat (limited to 'synapse/federation/transport')
-rw-r--r-- | synapse/federation/transport/client.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/synapse/federation/transport/client.py b/synapse/federation/transport/client.py index b5e4b2680e..fab4800717 100644 --- a/synapse/federation/transport/client.py +++ b/synapse/federation/transport/client.py @@ -431,7 +431,7 @@ class TransportLayerClient: The remote homeserver can optionally return some state from the room. The response dictionary is in the form: - {"knock_state_events": [<state event dict>, ...]} + {"knock_room_state": [<state event dict>, ...]} The list of state events may be empty. """ |