Currently, all error boundaries close audio and Apollo connections once
an error is caught. This is not the correct behavior as not all error
boundaries are critical, e.g.: the presentation crashing should _not_
break the whole client. It also deviates from how error boundaries
worked in 2.7
Add a new prop to the ErrorBoundary/LocatedErrorBoundary components
called isCritical that flags an error boundary instance as critical. If
true, it'll close Apollo/audio. The default behavior is
isCritical=false, and the only critical error boundaries are the ones
located in the app's root (/client/main.tsx).
I found a failed recording where a deskshare video file could not be
decoded when seeking was used (oddly enough, it could decode without
seeking). Turns out that remuxing the file was enough to make things
work.
In the video processing code, after checking for other known video file
problems that are fixed by remuxing, also try decoding one frame of the
video with a seek time applied.
Since more videos can end up being remuxed now, I moved the output of
the remux to a new subdirectory. Since more file types than just 'flv'
can be remuxed, I switched the output to the 'nut' container instead.
(This is ffmpeg's generic container format, and can hold any audio/video
which ffmpeg can process, so it works well for temporary files.)
It was recommended by Danimo because /etc is for mutable stuff
It also adds comments with context about this file
The owner is set to root:root and permission 600 to be only readable by root (also Danimo suggestion)
* fix first wheel zoom always going to top left corner
* focus button zoom on center of page after wheel zoom
* test: update zoom test to avoid snapshot miscomparisons when zooming in and out
* test: fix usage of hasText function params
---------
Co-authored-by: Anton B <antonbsa.bck@gmail.com>
* feat(screenshare): add support for troubleshooting links
Adds setting option to specify troubleshooting links to each error code
of screenshare. When a troubleshooting link for the given error exists,
the toast notification about the error is displayed with a 'Learn more'
button that when clicked leads the user to the external link. When there
is no link set for the specific error code, the button is not displayed.
* fix(screenshare): change toast type for error code 1136
Changed toast type from 'error' to 'warning' for error code 1136 when
sharing screen. This adjustment was made because error code 1136 is also
returned when the user cancels screen sharing during the tab selection
process. Displaying an error toast in this situation could cause
unnecessary alarm for users, as they were simply canceling an operation.
* fix(notification): help link button element
Uses the button element instead of a div to display the 'Learn more'
help link button.
---------
Co-authored-by: Carlos Henrique <carloshsc1998@gmail.com>
* 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
