Skip to content

fix: make debug logging work and not cause infinite updates #380

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: release52
Choose a base branch
from

Conversation

ianshade
Copy link
Contributor

About the Contributor

This pull request is posted on behalf of TV 2 Norge

Type of Contribution

This is a:

Bug fix

Current Behavior

The Activate debug logging for device option seemingly does nothing. No debug logs are printed when toggled on. However, when toggled while a device is already enabled, it causes an infinite sequence of update operations.

New Behavior

Debug logging works, and the operation updates properties needed for later comparison with potentially changed options. Null/undefined values are treated correctly.

Testing Instructions

  • Enable a device after setting Activate debug logging for device option to on and off. Check if there's a difference in logs depending on the value.
  • While a device is enabled, toggle Activate debug logging for device option on and off. Check if there's a difference in logs depending on the value.

In both cases, a device capable of outputting debug logs should be used, and playout actions should be performed in order to provoke the logs.

Other Information

Draft. Might add unit tests

Status

  • PR is ready to be reviewed.
  • The functionality has been tested by the author.
  • Relevant unit tests has been added / updated.
  • Relevant documentation (code comments, system documentation) has been added / updated.

@codecov-commenter
Copy link

codecov-commenter commented Jun 12, 2025

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...ne-state-resolver/src/service/ConnectionManager.ts 33.33% 2 Missing ⚠️

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants