Quentin Gliech 4af33015af Fix joining remote rooms when a on_new_event callback is registered (#16973) ... Since Synapse 1.76.0, any module which registers a `on_new_event` callback would brick the ability to join remote rooms. This is because this callback tried to get the full state of the room, which would end up in a deadlock. Related: https://github.com/matrix-org/synapse-auto-accept-invite/issues/18 The following module would brick the ability to join remote rooms: ```python from typing import Any, Dict, Literal, Union import logging from synapse.module_api import ModuleApi, EventBase logger = logging.getLogger(__name__) class MyModule: def __init__(self, config: None, api: ModuleApi): self._api = api self._config = config self._api.register_third_party_rules_callbacks( on_new_event=self.on_new_event, ) async def on_new_event(self, event: EventBase, _state_map: Any) -> None: logger.info(f"Received new event: {event}") @staticmethod def parse_config(_config: Dict[str, Any]) -> None: return None ``` This is technically a breaking change, as we are now passing partial state on the `on_new_event` callback. However, this callback was broken for federated rooms since 1.76.0, and local rooms have full state anyway, so it's unlikely that it would change anything.		2024-03-06 16:00:20 +01:00
..
.gitignore
16768.doc	Add HAProxy example for single port operation (#16768)	2024-02-20 16:15:58 +00:00
16946.doc	Better complement docs (#16946)	2024-02-20 17:14:50 +00:00
16951.doc	Add docs on upgrading from a very old version (#16951)	2024-02-22 17:36:41 +00:00
16973.bugfix	Fix joining remote rooms when a on_new_event callback is registered (#16973)	2024-03-06 16:00:20 +01:00