Skip to content

fix: Previously picked user wrongfully notified in next random selections #75

Merged
antobinary merged 2 commits intobigbluebutton:v0.0.xfrom
GuiLeme:fix-notification-when-not-picked
Sep 12, 2025
Merged

fix: Previously picked user wrongfully notified in next random selections #75
antobinary merged 2 commits intobigbluebutton:v0.0.xfrom
GuiLeme:fix-notification-when-not-picked

Conversation

@GuiLeme
Copy link
Collaborator

@GuiLeme GuiLeme commented Sep 11, 2025

What does this PR do?

It fixes a problem described ahead:

Suppose we have a meeting with a moderator (M), and 3 viewers (A, B and C):

  • M runs pick-random-user which selects A, for instance;
  • Ping sounds to A;
  • M runs pick-random-user again which selects B, this time;
  • Ping sounds for both A and B;
  • So on...

This error does not occur everytime, but is sort of frequent;

More

Most of the notification/ping flow was refactored in this PR to be, supposedly, cleaner, more readable and less complex. In order words, it would be good to test other scenarios as well to see if everything keeps working, such as not ping again when reloading the page, not ping multiple times, and so on...

@GuiLeme GuiLeme requested a review from antobinary September 11, 2025 14:10
@antobinary antobinary merged commit 7259ec7 into bigbluebutton:v0.0.x Sep 12, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants