Repository navigation
Log the Teams meeting research at debug level only - #42
Merged
Merged
Conversation
Yannicked
added this pull request to stack #44
October 14, 2026 13:53
Yannicked
force-pushed
the
fix/call-logging
branch
from
October 14, 2026 13:59
9417283 to
6f90f89
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #41.
The log file takes info by default, so the research logging from #36/#37 went to disk in every meeting. These are now debug (shown with
--verbose): a nameless participant's details and device metadata (which may name them),csrcInfopushes (up to 2000 characters), RTCP application payloads, each speaker history, and each camera or share request. The dumps also skip building their JSON and hex when debug is off.Looked at and left: sign-in logs the Teams tenant id at info, and error toasts are logged word for word.