- Ya
- 14 Agosti 2026, 23:51 UTC
- Mwandishi
- kamo
- Ahadi ya
- e9cc1f4
A reminder was arriving twice. The deck picks it up as a notification, and the older path picked it up as well: CalendarWebSocketContext opened a second STOMP connection to EmailService purely to listen on **************** and hand what it heard to ReminderPopup, a Snackbar pinned to the top-right corner. So one event announced itself in two corners of the screen, in two visual languages, with two sounds — the deck's own on arrival, and this path's playEventSound in the subscribe handler, which is why removing only the popup would have left the member hearing the reminder twice and seeing it once. Both are gone, and the context with them: nothing else consumed it, so it was a whole second websocket per member kept open to feed one popup. MeetReminderPopup stays. It looks the same and sits in the same corner, but it is fed by MediaService on /topic/meet/reminder/{member} for a meeting about to start — a different event from a different service, not a second copy of this one.