Skip to content
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

[Video] Fix Episode NFO parsing error (introduced in #24565) #25198

Merged
merged 1 commit into from May 15, 2024

Conversation

78andyp
Copy link
Contributor

@78andyp 78andyp commented May 11, 2024

Description

As reported in the forum https://forum.kodi.tv/showthread.php?tid=377480.

Error introduced in #24565 (I cannot reproduce the problem I was attempting to fix).

Also removed unneeded #include.

Motivation and context

Fix episode NFO parsing

How has this been tested?

Locally

What is the effect on users?

As above.

Screenshots (if appropriate):

Types of change

  • Bug fix (non-breaking change which fixes an issue)
  • Clean up (non-breaking change which removes non-working, unmaintained functionality)
  • Improvement (non-breaking change which improves existing functionality)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that will cause existing functionality to change)
  • Cosmetic change (non-breaking change that doesn't touch code)
  • Student submission (PR was done for educational purposes and will be treated as such)
  • None of the above (please explain below)

Checklist:

  • My code follows the Code Guidelines of this project
  • My change requires a change to the documentation, either Doxygen or wiki
  • I have updated the documentation accordingly
  • I have read the Contributing document
  • I have added tests to cover my change
  • All new and existing tests passed

@KarellenX
Copy link
Member

Thank you @78andyp

@fuzzard do you mind kicking off a test build?

@fuzzard
Copy link
Contributor

fuzzard commented May 12, 2024

@KarellenX
Copy link
Member

Thanks @fuzzard

@KarellenX
Copy link
Member

Tested this fix and multi-episodes are now scanned into the library correctly. Performed a few other scans as well with and without nfo files, using local and tmdb scraper, and I could find no further problems.

Thanks for the quick fix @78andyp
Maybe a backport as well when you have time?

@fuzzard fuzzard added this to the "P" 22.0 Alpha 1 milestone May 12, 2024
@fuzzard fuzzard added Type: Fix non-breaking change which fixes an issue Backport: Needed v22 "P" labels May 12, 2024
@CrystalP
Copy link
Contributor

Reverting the previous change is good.
However did you check that each episode of a multi-episode received the correct details? I'm not familiar with that code and it looks a little weird to me. Maybe all episodes receive the same details instead of details of episode 1, 2, etc. respectively. Haven't had the chance to runtime test yet.

@KarellenX
Copy link
Member

However did you check that each episode of a multi-episode received the correct details?

Yes, I checked. Title, Plot, Writers, Directors are correct for each episode.
Let me know if there is something else that needs checking.

78andyp added a commit to 78andyp/xbmc that referenced this pull request May 12, 2024
Copy link
Contributor

@CrystalP CrystalP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverting the code fixes the incorrect m_headPos for the later GetDetails calls.

@CrystalP
Copy link
Contributor

CrystalP commented May 12, 2024

Let me know if there is something else that needs checking.

No that's OK, thanks. I stepped through the code to understand what's happening.

@CrystalP CrystalP merged commit e695371 into xbmc:master May 15, 2024
2 checks passed
@78andyp 78andyp deleted the nfofix branch May 25, 2024 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport: Needed Type: Fix non-breaking change which fixes an issue v22 "P"
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants