user-left webhook not working in some cases
@prlanzarin is already working on this.
Since Mar 27, 2024.
Assessment
This issue has not been assessed yet.
Description
Describe the bug
"user-left" webhook not working in 3 cases (1 case - not sure if it's a feature or a bug).
- The meeting is running, but the moderator left. (We set "end meeting when no moderator minutes" to 5, so it would wait for the moderator to come back before the meeting automatically ends).
- A user (viewer) leaves the meeting and after 1 or 2 seconds, the moderator ends the meeting.
- A meeting is running. A user (viewer) joins and leaves within a few seconds. <- This doesn't happen all the time. This happens once in 10-15 times.
- I'm not sure if this is valid. Users (all viewers) are there in the meeting. The moderator ends the meeting. "user-left" web-hook for all the users, who were in the meeting right before the meeting ended, is not called.
Expected behavior
- The meeting is running, but the moderator left. => we should get "user-left" webhook for the moderator.
- A user (viewer) leaves the meeting and after 1 or 2 seconds, the moderator ends the meeting. => We should get "user-left" webhook for all the users who left the meeting right before the meeting ended.
- A meeting is running. A user (viewer) joins and leaves within a few seconds. => we should get "user-left" web-hook
- I'm not sure if this is valid. Users (all viewers) are there in the meeting. The moderator ends the meeting. "user-left" web-hook for all the users, who were in the meeting right before the meeting ended, is not called. => we should probably get "user-left" web-hook for all the users who were in the meeting right before the meeting ended.
Please tell me if you need additional details or more context.
Tested in BBB Version : 2.7.5
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bigbluebutton/bbb-webhooks
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
"eventID" filtering does not work، when we set the hook as "Persistent Hook"!May be free again @prlanzarin claimed this 1108 days ago, and no pull request is open. Openstatus: verify type: enhancement v3
bigbluebutton/bbb-webhooks#19 · 1 comment · 1 assignee ·
-
module: webhook status: accepted type: enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in bigbluebutton/bbb-webhooks
Similar issues
-
ai bug design good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
neomjs/neo-agent-institution#927 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gramps-project/gramps-web#1671 ·
Maintainers usually reply within 1 day
-
bug good first issue priority: P2 status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RhinoLink-Tech/data-fabric#502 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cline/mcp-marketplace#3708 ·
-
beginner-friendly category:finding-titles community enhancement first-timers-only good first issue help wanted low hanging fruit micro-contribution type: task up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Berserk-hub150/skillhawk#264 · 1 comment ·
Maintainers usually reply within 4 days