From ec33a40201e1086cb5ff0548e409abc35f0ce056 Mon Sep 17 00:00:00 2001 From: Eric Eastwood Date: Wed, 15 Dec 2021 23:20:53 -0600 Subject: Make the historical events float separately from the state chain See https://github.com/matrix-org/synapse/pull/11114#discussion_r760843910 --- synapse/rest/client/room_batch.py | 9 --------- 1 file changed, 9 deletions(-) (limited to 'synapse/rest/client/room_batch.py') diff --git a/synapse/rest/client/room_batch.py b/synapse/rest/client/room_batch.py index c9509d2ae3..4b6be38327 100644 --- a/synapse/rest/client/room_batch.py +++ b/synapse/rest/client/room_batch.py @@ -205,21 +205,12 @@ class RoomBatchSendEventRestServlet(RestServlet): EventContentFields.MSC2716_NEXT_BATCH_ID ] - # Also connect the historical event chain to the end of the floating - # state chain, which causes the HS to ask for the state at the start of - # the batch later. If there is no state chain to connect to, just make - # the insertion event float itself. - prev_event_ids = [] - if len(state_event_ids_at_start): - prev_event_ids = [state_event_ids_at_start[-1]] - # Create and persist all of the historical events as well as insertion # and batch meta events to make the batch navigable in the DAG. event_ids, next_batch_id = await self.room_batch_handler.handle_batch_of_events( events_to_create=events_to_create, room_id=room_id, batch_id_to_connect_to=batch_id_to_connect_to, - initial_prev_event_ids=prev_event_ids, inherited_depth=inherited_depth, auth_event_ids=auth_event_ids, app_service_requester=requester, -- cgit 1.5.1