* feat(layout): add propagation toggle
Transforms the 'update everyone' button in the layout modal into a
toggle, so that presenter get immediate visual feedback of the current
layout propagation setting when the modal is opened.
* fix: update propagation button locale to 'update to everyone'
* test: update layout test
---------
Co-authored-by: Anton B <antonbsa.bck@gmail.com>
Commit 325887e325 split the local echo audio
element from the main audio element to allow concurrent playback without the
risk of interfering with one another.
This introduced a regression where local echo doesn't track output device
changes. The main audio element (i.e. the meeting's audio) is not affected by
this regression.
This commit ensures local echo reacts to output device changes as needed.
This commit introduces `userLockSettings`, which includes an option to set `disablePublicChat` for specific users, rather than only for all locked viewers as before. This implementation covers the backend and GraphQL portions; the frontend changes will be addressed in a separate PR.
This is a port of #20585, originally implemented for version 2.7 using the old architecture with MongoDB.
The changes in [PR #20782](https://github.com/bigbluebutton/bigbluebutton/pull/20782)
do not mean that enabling `transparentListenOnly: true` sets `listenOnlyMode: false`.
I.e., the user prompt to choose between mic or listen-only still exists. Instead, it
allows users to seamlessly switch between modes without rejoining audio.
While the goal is for `transparentListenOnly: true` to eventually imply `listenOnlyMode:
false`, the default audio activation behavior is still under review by the UI team, and
the current default remains unchanged.
This commit updates the "What's New" documentation to reflect these points correctly.
* docs: various docs updates to include what is new
in BBB 3.0.0-beta.1
- api changes
- dropped functionality
* docs: info on infinite whiteboard and seen chat
Adding screenshots and descriptions about the infinite whiteboard and
seen private chat messages to the 3.0 what-is-new docs
* docs: Add description of 3.0 new audio features
- improved ux for transparent listen only
- push to talk
In BBB ≤ 2.7, a procedure monitored system audio device changes, updating
the device list and assigning a fallback device if the current one was removed.
This procedure was removed in 3.0 during the migration of the
input-stream-live-selector component to TypeScript (reasons unknown), causing
the device list to become outdated and leaving the user's client without audio
input if their current device is disconnected.
This commit restores the `devicechange` event handler in the input-stream-live-
selector, ensuring that the device list is updated properly and fallback devices
are assigned when necessary.
* Introduce Hasura override config and a password file
* Add message when set a password to Hasura
* add logs to inspect errors
* fix config file name
* test changing key file owner
* test without override file
* fix print status
* store password as env var
* changes suggested in PR
* Introduce Gql-Middleware config as a yml file
* use path /usr/share/bbb-graphql-middleware/ instead of /usr/local/bigbluebutton/bbb-graphql-middleware
* remove /etc/default/bbb-graphql-middleware file
Adjust an inline comment in connection status' service about packet loss metric
usage.
Now it correctly states that the absolute counter SHOULD NOT be used for
alert triggers.
In 3.0, the packet loss metric used to trigger connection status alerts was
changed to the one generated by the `startMonitoringNetwork` method used by the
connection status modal. Since packet loss thresholds were not adjusted (0.5,
0.1, 0.2), a single lost packet causes the status alert to be permanently
stuck on "critical". This is explained by how different those metrics
are:
- **Before (2.7):** A 5-probe wide calculation of inbound packet loss
fraction based on `packetsLost` and `packetsReceived` metrics.
- **Now (3.0):** An absolute counter of inbound lost packets.
This commit restores the previous packet loss metric used to trigger
connection status alerts, reverting to the original collection method via
`/utils/stats.js`. This resolves the issue, but further work is needed in
subsequent PRs:
- Unify the collection done in `/utils/stats.js` with the
`startMonitoringNetwork` method.
- Incorporate the remote-inbound `fractionsLost` metric to account for packet
loss on both legs of the network (in/out).
- Update the packet loss metric displayed in the connection status modal to
show a more meaningful value (e.g., packet loss percentage over a specific
probe interval). An absolute counter of lost packets isn't useful for end
users.
- Update the alert log to use the fraction or percentage above
