Fixes
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
fix(ProxyConnection) set signaling layer by @saghul in #1862
fix: Fixes version while building. by @damencho in #1866
feat(multi-stream-support)Add support for multiple local and remote tracks/mediaType. by @jallamsetty1 in #1861
fix: Add private message handler for breakout_rooms by @steve-vsee in #1867
fix(JingleSessionPC) Do not force track removal at pc level on user leave. by @jallamsetty1 in #1869
feat(multi-stream-support) Handle SDP munging for multiple local/remote streams per ep. by @jallamsetty1 in #1868
They don't render the toolbar so there is more space available.
The reason this commit does that is because getToolboxHeight will now
always be 0 for recorders.
* fix(facial-expressions): set window screen size from worker with the value from main thread
* fix(facial-expressions): refactor worker and add constants for message types
Workaround for the issue when the mouse enter event is not triggered in
the use case where the layout changes and the mouse appears onn top of the
thumbnail. Example: Closing the participant pane.
Fixes an issue where on clean install we see:
WARNING: [25] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#622: [MucClient id=shard hostname=localhost] error connecting
org.jivesoftware.smack.SmackException$SmackWrappedException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
This notification is missing in the array. If array is selectively defined, no pop-up notification is received when participant requests to join the meeting.
Added config to choose between recording and always mode
Created function to check if feature should be used
Removed check from stop feature as it now checks if the feature was previously on
Only get video track on feature start
This has 2 benefits:
a) it no longer needs to be built at install time, thus making builds faster
before:
real 0m46.865s
user 1m3.938s
sys 0m22.478s
after:
real 0m27.828s
user 0m25.582s
sys 0m21.699s
b) integrity errors go away since they are not computed over a locally
generated tarball
JohnProv
Christoph Settgast
Calin Chitu
Jaya Allamsetty
Saúl Ibarra Corretgé
Gabriel Borlea
Mihaela Dumitru
Besnik Bleta
Calinteodor
Tudor D. Pop
Hristo Terezov
Gabriel Borlea
Ali Alhaidary
Дамян Минков
Robert Pintilii
Freddie
Shawn Chin
Santiago Vila
ONO Yoshio
wfleischer
Shawn