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 cache #40

Merged
merged 3 commits into from
Jan 25, 2025
Merged

fix:improve cache #40

merged 3 commits into from
Jan 25, 2025

Conversation

JarbasAl
Copy link
Member

@JarbasAl JarbasAl commented Jan 25, 2025

cache domain intents in their own folder to avoid retraining when config changes

improve error handling

Summary by CodeRabbit

  • New Features

    • Enhanced intent matching process with more flexible caching and stemming options.
    • Improved training manager with better logging and error handling.
  • Bug Fixes

    • Resolved potential inconsistencies in hash generation for training data.
    • Improved thread safety during the training process.
  • Chores

    • Streamlined code for better readability and maintainability.
    • Added more detailed debug logging for training operations.

cache domain intents in their own folder to avoid retraining when config changes

improve error handling
Copy link

coderabbitai bot commented Jan 25, 2025

Warning

Rate limit exceeded

@JarbasAl has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 24 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 2eae6e5 and 7ca51b5.

📒 Files selected for processing (1)
  • tests/test_util.py (1 hunks)

Walkthrough

The pull request introduces modifications to the Padatious intent matching system, focusing on improving intent caching, stemming functionality, and training management. The changes enhance the flexibility of intent processing by adding a use_stemmer configuration option, updating caching mechanisms, and improving the training process with better logging and error handling. The modifications aim to provide more robust and configurable intent matching capabilities.

Changes

File Change Summary
ovos_padatious/opm.py - Added use_stemmer variable to control stemming
- Updated intent cache path construction
- Modified container initialization with pre-loading
- Streamlined stemmer initialization logic
ovos_padatious/training_manager.py - Added debug logging for training process
- Improved error handling in training methods
- Implemented thread-safe training object processing
ovos_padatious/util.py - Modified lines_hash function to sort lines before hashing
- Ensures consistent hash generation regardless of line order

Sequence Diagram

sequenceDiagram
    participant PM as PadatiousPipeline
    participant TM as TrainingManager
    participant IC as IntentContainer

    PM->>PM: Configure use_stemmer
    PM->>IC: Initialize with pre-loaded cache
    TM->>TM: Add training objects
    TM->>TM: Log training details
    TM->>IC: Train objects
    TM->>TM: Track failed training attempts
Loading

Possibly related PRs

Poem

🐰 In the realm of intents so bright,
Stemming and caching take their flight,
Padatious dances with grace and might,
Sorting lines, making hashes just right,
A rabbit's code brings pure delight! 🔍


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.

@github-actions github-actions bot added fix and removed fix labels Jan 25, 2025
Copy link

@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: 1

🧹 Nitpick comments (1)
ovos_padatious/training_manager.py (1)

156-163: Consider adding a retry mechanism with backoff.

While the error handling is good, implementing a retry mechanism with exponential backoff could help recover from temporary failures.

from time import sleep
from random import uniform

def retry_with_backoff(func, max_retries=3):
    """Retry a function with exponential backoff."""
    for i in range(max_retries):
        try:
            return func()
        except Exception as e:
            if i == max_retries - 1:
                raise
            sleep_time = (2 ** i) + uniform(0, 1)
            sleep(sleep_time)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 97149f8 and 5828a3e.

📒 Files selected for processing (3)
  • ovos_padatious/opm.py (1 hunks)
  • ovos_padatious/training_manager.py (2 hunks)
  • ovos_padatious/util.py (1 hunks)
🔇 Additional comments (5)
ovos_padatious/training_manager.py (3)

88-91: LGTM! Enhanced logging improves debugging capabilities.

The added debug logs provide better visibility into training decisions, clearly indicating first-time training scenarios and hash changes.


145-146: LGTM! Thread safety improvement.

Creating a copy of objects_to_train prevents potential concurrent modification issues during training.


148-153: LGTM! Robust error handling for training failures.

The try-except block gracefully handles training failures, logs errors, and maintains failed objects for potential retry, improving system resilience.

ovos_padatious/opm.py (1)

277-286: LGTM! Well-organized cache directory structure.

The cache directory organization cleanly separates different configurations (domain vs. regular, stemmer vs. non-stemmer), preventing cache conflicts.

ovos_padatious/util.py (1)

31-31: LGTM! Improved hash consistency.

Sorting lines before hashing ensures consistent cache keys regardless of line order, preventing unnecessary retraining.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@github-actions github-actions bot added fix and removed fix labels Jan 25, 2025
Copy link

@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 (1)
ovos_padatious/opm.py (1)

Line range hint 297-301: Add debug logging for stemmer initialization.

Consider adding debug logging to indicate when stemming is enabled/disabled and which languages have stemmer support.

         if use_stemmer:
+            LOG.debug(f"Initializing stemmers with stemming enabled")
             self.stemmers = {lang: Stemmer(lang)
                              for lang in langs if Stemmer.supports_lang(lang)}
+            LOG.debug(f"Initialized stemmers for languages: {list(self.stemmers.keys())}")
         else:
+            LOG.debug("Stemming disabled, skipping stemmer initialization")
             self.stemmers = {}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5828a3e and 2eae6e5.

📒 Files selected for processing (1)
  • ovos_padatious/opm.py (1 hunks)
🔇 Additional comments (2)
ovos_padatious/opm.py (2)

277-286: LGTM! Improved caching mechanism with better organization.

The changes enhance the caching system by:

  1. Separating domain intents into their own cache folder with _domain suffix
  2. Adding a stemmer-specific cache folder with _stemmer suffix when stemming is enabled

This prevents unnecessary retraining when switching between configurations, improving efficiency.


290-295: LGTM! Implemented error handling for pre-loading cached intents.

The implementation matches the previously suggested error handling improvement, ensuring graceful handling of failures during pre-loading of cached intents.

cache domain intents in their own folder to avoid retraining when config changes

improve error handling
@JarbasAl JarbasAl merged commit 4e2c2ce into dev Jan 25, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant