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

fix: improve season validation logic in torrent parsing #1011

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

davidemarcoli
Copy link
Collaborator

@davidemarcoli davidemarcoli commented Feb 21, 2025

Pull Request Check List

Resolves: #issue-number-here

  • Added tests for changed code.
  • Updated documentation for changed code.

Description:

Summary by CodeRabbit

  • Bug Fixes
    • Refined media content matching to improve torrent selection accuracy. The system now permits slight discrepancies by allowing up to one missing season, ensuring more reliable series content identification.
    • Users can enjoy improved result consistency as the updated evaluation minimizes false negatives and better aligns available content with expectations.
    • Overall, these improvements enhance content reliability and refine the viewing experience.

Copy link
Contributor

coderabbitai bot commented Feb 21, 2025

Walkthrough

The pull request refines the season validation logic within the _parse_results function. The new implementation uses a list comprehension to identify specific missing seasons, allowing for at most one missing season, rather than merely comparing counts. Enhanced debug logging now records the exact missing season(s) when a torrent is either accepted or skipped, improving traceability.

Changes

File(s) Change Summary
src/program/.../shared.py Updated _parse_results function to evaluate torrents for shows by checking for specific missing seasons using a list comprehension. Improved debug logging to indicate when a torrent is added or skipped, detailing any missing season(s).

Sequence Diagram(s)

sequenceDiagram
    participant S as Scraper Service
    participant P as _parse_results
    participant L as Logger

    S->>P: Process torrent results
    P->>P: Identify missing seasons via list comprehension
    alt At most one missing season
        P->>L: Log debug message for accepted torrent (missing season details)
        P-->>S: Return accepted torrent
    else More than one missing season
        P->>L: Log debug message for skipped torrent (list missing seasons)
        P-->>S: Return skipped torrent
    end
Loading

Suggested reviewers

  • iPromKnight
  • dreulavelle

Poem

I'm a hopping coder in the digital glade,
Seasons now checked with a smarter cascade.
One missing? No fret, debug logs cheer,
In a world of torrents, the path is clear.
Hop on, friends, let the changes endear!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (3)
src/program/services/scrapers/shared.py (3)

99-101: Add type hints and improve comment clarity.

The list comprehension and condition would benefit from type hints and a more detailed comment explaining the rationale.

-    # Check if torrent has most of the seasons we need
-    missing_seasons = [season for season in needed_seasons if season not in torrent.data.seasons]
-    if len(missing_seasons) <= 1:  # Allow at most 1 missing season because Trakt doesn't always index shows according to uploaders
+    # Allow at most 1 missing season to handle Trakt indexing discrepancies
+    # For example: If Trakt lists seasons 1-4 but uploaders consider seasons 1-3 as complete
+    missing_seasons: list[int] = [season for season in needed_seasons if season not in torrent.data.seasons]
+    if len(missing_seasons) <= 1:

99-107: Add unit tests for the season validation logic.

The changes to the season validation logic need test coverage to ensure reliability. Consider adding tests for:

  1. Torrent with all needed seasons
  2. Torrent missing one season (should be accepted)
  3. Torrent missing multiple seasons (should be rejected)
  4. Edge cases like empty season lists

Would you like me to help create these test cases? I can generate a test suite that covers these scenarios.


99-107: Update documentation to reflect the new season validation behavior.

The changes to how missing seasons are handled should be documented to help users understand when torrents will be accepted or rejected.

Would you like me to help draft documentation that explains:

  1. The "one missing season" rule
  2. Why this leniency exists (Trakt indexing discrepancies)
  3. How to use the debug logs to understand torrent acceptance/rejection
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2523993 and 23a7cfd.

📒 Files selected for processing (1)
  • src/program/services/scrapers/shared.py (1 hunks)

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

Successfully merging this pull request may close these issues.

1 participant