fix: persona name , add models

[JarbasAl]

Summary by CodeRabbit

• New Features
  • Persona configurations now automatically default to a valid name when none is provided, ensuring consistent naming.
  • The status endpoint now returns enhanced details, including solver model configurations for improved transparency.

[coderabbitai]

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 14 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 df172c0 and 9f00f1d.

📒 Files selected for processing (1)

• ovos_persona_server/__init__.py (1 hunks)

Walkthrough

This pull request updates how the name attribute is assigned within the get_app function. The change now sets persona["name"] to either the existing value or the base name from the persona_json if not provided. Additionally, the instantiation of the Persona object uses the name from the dictionary. The /status route has also been enhanced to include a new models key mapping each solver to its model configuration.

Changes

File	Change Summary
ovos_persona_server/init.py	Updated the get_app function to set persona["name"] (using the JSON file’s base name as fallback) and instantiate Persona with this value. Enhanced /status endpoint to include a models key mapping solver names to their model configurations.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant App as get_app()
    participant File as persona_json File
    participant Persona

    Client->>App: Call get_app()
    App->>File: Read persona_json
    File-->>App: Return persona data
    App->>App: Set persona["name"] (fallback if missing)
    App->>Persona: Instantiate Persona with persona["name"]
    Persona-->>App: Created Persona

    Client->>App: Request /status
    App->>Client: Return response with solvers and models mapping

Loading

Poem

I'm hopping through lines of code with glee,
Changing names with a twist of key.
A persona reborn from file's own guise,
And /status now unveils models wise.
In my rabbit world, each change is a treat,
A cheerful dance in every beat!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
• @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.