Wrapping happens at 88 chars

See https://github.com/matrix-org/synapse/pull/13958#discussion_r984106210

1 files changed, 10 insertions, 12 deletions

diff --git a/synapse/storage/databases/main/roommember.py b/synapse/storage/databases/main/roommember.py
index 8a9e553397..5230efffb1 100644
--- a/synapse/storage/databases/main/roommember.py
+++ b/synapse/storage/databases/main/roommember.py
@@ -152,18 +152,16 @@ class RoomMemberWorkerStore(EventsWorkerStore):
         `get_current_hosts_in_room()` and so we can re-use the cache but it's
         not horrible to have here either.
 
-        Uses `m.room.member`s in the room state at the current forward
-        extremities to determine which users are in the room.
-
-        Will return inaccurate results for rooms with partial state, since the
-        state for the forward extremities of those rooms will exclude most
-        members. We may also calculate room state incorrectly for such rooms and
-        believe that a member is or is not in the room when the opposite is
-        true.
-
-        Note: If you only care about users in the room local to the homeserver,
-        use `get_local_users_in_room(...)` instead which will be more
-        performant.
+        Uses `m.room.member`s in the room state at the current forward extremities to
+        determine which users are in the room.
+
+        Will return inaccurate results for rooms with partial state, since the state for
+        the forward extremities of those rooms will exclude most members. We may also
+        calculate room state incorrectly for such rooms and believe that a member is or
+        is not in the room when the opposite is true.
+
+        Note: If you only care about users in the room local to the homeserver, use
+        `get_local_users_in_room(...)` instead which will be more performant.
         """
         return await self.db_pool.runInteraction(
             "get_users_in_room", self.get_users_in_room_txn, room_id