[pvr] Fix errors after switching from using backend channel numbers to using kodi channel numbers and vica versa #8204
Conversation
This file contains 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
…o using kodi channel numbers and vica versa
ksooo
added
Type: Fix
|
This fix would be valid for Isengard as well since the regression was introduced some time after Helix was released. |
|
@Jalle19 imo this is just an edge case not worth backporting. Fine with that? |
|
Okay, fine by me. |
|
jenkins build this please |
ksooo
added a commit
that referenced
this pull request
Oct 13, 2015
[pvr] Fix errors after switching from using backend channel numbers to using kodi channel numbers and vica versa
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.
When switching between "use backend channel numbers" and "use kodi backend numbers" and not restarting kodi after that, one might have ended up with switching to the wrong channel or to no channel at all for certain channels, if the backend version numbers have "gaps". This PR fixes this.
@negge mind taking a look (We talked about this bug at DevCon).