Fix duplicate PlutoTV service references when channels share the same number#22
Closed
xcentaurix wants to merge 1 commit into
Closed
Fix duplicate PlutoTV service references when channels share the same number#22xcentaurix wants to merge 1 commit into
xcentaurix wants to merge 1 commit into
Conversation
Contributor
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
2 participants
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.
This PR fixes an issue where two different PlutoTV channels could generate the same Enigma2 service reference, which caused channel collisions in bouquets.
Example of the problem:
Two channels with different Pluto channel IDs could end up with identical SID/TSID based references.
This resulted in duplicate #SERVICE entries for different channels.