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

feat:persona pipeline #648

Merged
merged 5 commits into from
Jan 31, 2025
Merged

feat:persona pipeline #648

merged 5 commits into from
Jan 31, 2025

Conversation

JarbasAl
Copy link
Member

@JarbasAl JarbasAl commented Jan 31, 2025

support for https://github.com/OpenVoiceOS/OVOS-persona while we wait for #437

to enable

{
  "intents": {
      "pipeline": [
          "stop_high",
          "converse",
          "ocp_high",
          "padatious_high",
          "adapt_high",
          "ovos-persona-pipeline-plugin-high",
          "ocp_medium",
          "fallback_high",
          "stop_medium",
          "adapt_medium",
          "padatious_medium",
          "adapt_low",
          "common_qa",
          "fallback_medium",
          "ovos-persona-pipeline-plugin-low",
          "fallback_low"
    ]
  }
}

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Integrated PersonaService to enhance intent matching capabilities.
    • Added support for high and low priority persona-related intent matching.
  • Dependencies

    • Added ovos-persona package (version >=0.4.1, <1.0.0).

Copy link

coderabbitai bot commented Jan 31, 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 12 minutes and 47 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 2ae0e50 and c659fa3.

📒 Files selected for processing (1)
  • requirements/requirements.txt (1 hunks)

Walkthrough

The pull request introduces integration of the PersonaService into the IntentService within the OVOS core. This change adds support for new persona-based intent matching functions with high and low priority levels. The modification involves importing the PersonaService, initializing an instance within the IntentService, and extending the intent matching pipeline with two new matcher functions: ovos-persona-pipeline-plugin-high and ovos-persona-pipeline-plugin-low. Additionally, a new dependency on ovos-persona is specified in the requirements file.

Changes

File Change Summary
ovos_core/intent_services/__init__.py - Added import for PersonaService
- Initialized _persona instance in __init__ method
- Added ovos-persona-pipeline-plugin-high and ovos-persona-pipeline-plugin-low matchers to get_pipeline
requirements/requirements.txt - Added ovos-persona dependency with version constraint >=0.4.1,<1.0.0

Possibly related PRs

  • fix: logs and pipeline query api #636: This PR modifies the IntentService class in the same file as the main PR, indicating changes to the intent handling logic, which may interact with the new matcher functions added for PersonaService.
  • feat:multilang_match #646: This PR also alters the IntentService class, enhancing intent matching capabilities, which is directly related to the new functionality introduced by integrating PersonaService in the main PR.

Suggested reviewers

  • goldyfruit

Poem

🐰 Persona's dance, a matcher's delight,
Intents now flow with newfound might!
High and low, the rabbit's glee,
Matching magic, wild and free!
OVOS leaps with persona's spark! 🌟


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 feature and removed feature labels Jan 31, 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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 96d4fa1 and 7c5ab50.

📒 Files selected for processing (2)
  • ovos_core/intent_services/__init__.py (4 hunks)
  • requirements/requirements.txt (1 hunks)
🔇 Additional comments (5)
requirements/requirements.txt (1)

10-10: LGTM! Dependency version constraints are appropriate.

The version constraint >=0.4.0,<1.0.0 follows semantic versioning best practices, allowing minor updates while preventing major breaking changes.

ovos_core/intent_services/__init__.py (4)

36-36: LGTM! Import statement is correctly placed.

The PersonaService import is appropriately placed with other service imports.


117-117: LGTM! Service initialization follows established pattern.

The PersonaService is initialized consistently with other services, using the bus and config parameters.


209-210: LGTM! Pipeline integration aligns with PR objectives.

The persona matchers are correctly integrated into the pipeline:

  • persona_high is placed after converse stage
  • persona_low is placed before fallback_low stage

This matches the PR objectives exactly.


277-300: Documentation improvement is clear and comprehensive.

The added docstring for _emit_match_message follows good documentation practices with clear sections for Args, Details, Side Effects, and Returns.

ovos_core/intent_services/__init__.py Show resolved Hide resolved
@github-actions github-actions bot added feature and removed feature labels Jan 31, 2025
Copy link

codecov bot commented Jan 31, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.02%. Comparing base (23f0bab) to head (c659fa3).
Report is 174 commits behind head on dev.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #648      +/-   ##
==========================================
- Coverage   75.33%   71.02%   -4.32%     
==========================================
  Files          15       15              
  Lines        3094     1653    -1441     
==========================================
- Hits         2331     1174    -1157     
+ Misses        763      479     -284     
Flag Coverage Δ
end2end 54.56% <100.00%> (?)
unittests 47.61% <100.00%> (-27.73%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot added feature and removed feature labels Jan 31, 2025
@JarbasAl JarbasAl marked this pull request as draft January 31, 2025 03:00
@JarbasAl JarbasAl marked this pull request as ready for review January 31, 2025 05:26
@github-actions github-actions bot added feature and removed feature labels Jan 31, 2025
@JarbasAl JarbasAl merged commit 4c729a8 into dev Jan 31, 2025
8 of 9 checks passed
@JarbasAl JarbasAl deleted the feat/persona_pipeline branch January 31, 2025 06:16
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