-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a column participant
to room_memberships
table
#18068
base: develop
Are you sure you want to change the base?
Conversation
participant
to room_membership
tableparticipant
to room_memberships
table
Requesting @anoadragon453's feedback on this as he has context. |
synapse/handlers/message.py
Outdated
@@ -1440,6 +1440,9 @@ async def handle_new_client_event( | |||
) | |||
return prev_event | |||
|
|||
if event.type == "m.room.message": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drive by comment: presumably we also want to include encrypted messages here? Which have their own event type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Thanks for picking up on that :)
Delayed events complement test failure looks like a flake? |
Adds a column
participant
toroom_memberships
table to track whether a user has participated in a room - participation is defined as having sent am.room.message
orm.room.encrypted
event into the room.Related to #18040, the approach there to determine room participation was deemed too inefficient and adding this column was the recommend remedy.