[embyfin-stream-cleanup] Repeated INFO log spam: 'pools will be combined' fires 3× per poll cycle

[nemesbak]

Plugin

embyfin-stream-cleanup v1.2.0

Problem

_get_media_server_configs() uses logger.info(...) for the shared-identifier message, and that method is called three times per poll cycle:

1. In _poll_once() → directly calls _get_media_server_configs()
2. In _fetch_media_server_sessions() → also calls _get_media_server_configs()
3. In _fetch_active_recording_channels() → also calls _get_media_server_configs()

With a default poll interval of 10 seconds, this generates ~18 identical log lines per minute whenever two media servers share any identifier. Example:

INFO _dispatcharr_plugin_embyfin_stream_cleanup.handler Server 2: identifier(s) 192.168.1.25 also on a lower-numbered server — pools will be combined for those identifiers
INFO _dispatcharr_plugin_embyfin_stream_cleanup.handler Server 2: identifier(s) 192.168.1.25 also on a lower-numbered server — pools will be combined for those identifiers
INFO _dispatcharr_plugin_embyfin_stream_cleanup.handler Server 2: identifier(s) 192.168.1.25 also on a lower-numbered server — pools will be combined for those identifiers

(×3 every 10 seconds, non-stop)

Suggested fix

handler.py line 223: change logger.info → logger.debug.

# Before
logger.info(
    f"Server {n}: identifier(s) {', '.join(sorted(dupes))} also on a "
    "lower-numbered server — pools will be combined for those identifiers"
)

# After
logger.debug(
    f"Server {n}: identifier(s) {', '.join(sorted(dupes))} also on a "
    "lower-numbered server — pools will be combined for those identifiers"
)

The message is still available at DEBUG level for troubleshooting. In normal INFO-level operation it generates no output.

Setup that triggers it

Any configuration with two media server entries sharing the same identifier (e.g. one Jellyfin instance registered under both Server 1 and Server 2 slots, or both using the same IP as their identifier).

Attempted PR

Submitted PR #99 but was automatically closed — the repo policy requires the plugin author/maintainer to make changes. Reporting as an issue instead.

[sethwv]

Per the notes in the issue submission flow-

For issues with a specific plugin, find its thread in the Dispatcharr Discord or open an issue in the plugin's own repository.

This issue tracker & repo are for distribution. Please submit issues & PRs against the plugins' own repos.

[sethwv]

Also per the comment left on #99

PR Closed: Unauthorized
Your GitHub username (nemesbak) does not appear in author or maintainers for any of the plugin(s) in this PR. This PR has been automatically closed.
If you would like to contribute to this plugin, please consider reaching out to the maintainers of this plugin on Discord, or the plugin's Github repository.