Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

New server notices do not create a new room after previous was exited #5791

Closed
dkasak opened this issue Jul 30, 2019 · 2 comments · Fixed by #10679
Closed

New server notices do not create a new room after previous was exited #5791

dkasak opened this issue Jul 30, 2019 · 2 comments · Fixed by #10679
Labels
z-bug (Deprecated Label) z-p2 (Deprecated Label)

Comments

@dkasak
Copy link
Member

dkasak commented Jul 30, 2019

Description

After receiving a server notice, if a user exits the notices room, he won't be
invited to a new room when a new notice happens. In fact, the new notice gets
lost / is never received by the user.

Steps to reproduce

  1. Send server notice to a user via the _synapse/admin/v1/send_server_notice API.
  2. Have the user accept the invite and then exit the room.
  3. Send another server notice.

No new room is created for the new server notice from step 3 and it is
therefore never received.

Version information

  • Homeserver: https://termina.org.uk
  • Version: Synapse 1.2.1
  • Install method: FreeBSD ports collection
  • Platform: FreeBSD 11
@richvdh
Copy link
Member

richvdh commented Jul 30, 2019

this surprises me. The server-notices code checks that the user is still a member of the room, and should create a new room if not.

@dkasak
Copy link
Member Author

dkasak commented Jul 31, 2019

I just tried again and the bug is definitely there for me until I restart synapse. Then the user involved can receive notices again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
z-bug (Deprecated Label) z-p2 (Deprecated Label)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants