livekit

mirror of https://github.com/livekit/livekit.git synced 2026-03-31 21:55:41 +00:00

Files

Raja Subramanian d05d26cc04 Do not patch subscription setting when processing UpdateSubscription (#1247 )

message.

There are is a sequence where a dupe could be detected due to patching
which could lead to issues.

The sequence is
- UpdataTrackSettings with some values
- UpdateSubscription with Subcribe: false - this will patch from above
  track settings
- UpdateSubscription with Subscribe: true - this will continue patching
- UpdateTrackSettings with the same settings as in the first step - this
  will be declared a dupe because the track is enabled and the patched
  settings will declare no change in settings.

This is okay in the current code as subscription settings are cached at
participant level and applied when somebody re-subscribes. But, that
down stream processing can change any time.

So, when processing `UpdateSubscription` message, just do not patch.
If a later `UpdateTrackSettings` comes along, let it pass even if it
is not changing anything.

2022-12-21 11:12:40 +05:30

clientconfiguration

publish new codec when subscriber needed (#762 )

2022-06-16 18:16:34 +08:00

config

Validate keys to ensure sufficient security. (#1217 )

2022-12-07 22:25:28 -08:00

logger

Update to new logging library, using sampling participant logger (#1219 )

2022-12-09 00:09:03 -08:00

routing

Comment out memstats worker. (#1239 )