Skip to content

Fix: Correct provider name in config from openai to lm_studio #1570

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

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

Conversation

XavierMoon
Copy link

@XavierMoon XavierMoon commented Apr 18, 2025

PR Description
This PR fixes a typo in the config.lm_studio.yaml file where the provider was incorrectly set to openai instead of lm_studio. This caused local LLM services (such as LM Studio) to be unrecognized and unusable. Changes
Corrected the provider field from openai to lm_studio in the config file Ensured compatibility with local LLM services

Summary by CodeRabbit

  • Documentation
    • Updated configuration examples to use the "lm_studio/" model provider prefix instead of "openai/" for both language and embedding models. Comments were revised to match the new format.

PR Description
This PR fixes a typo in the config.lm_studio.yaml file where the provider was incorrectly set to openai instead of lm_studio. This caused local LLM services (such as LM Studio) to be unrecognized and unusable.
Changes
Corrected the provider field from openai to lm_studio in the config file
Ensured compatibility with local LLM services
Copy link
Contributor

coderabbitai bot commented Apr 18, 2025

Walkthrough

The configuration file for the language model service was updated to change the model provider prefix from "openai/" to "lm_studio/" for both the language model and embedding model entries. The corresponding comments were also revised to reflect this new prefix. No changes were made to other configuration parameters, endpoints, or settings, and no code or exported entities were altered.

Changes

File(s) Change Summary
docs/config_examples/config.lm_studio.yaml Updated model and embedder provider prefixes from "openai/" to "lm_studio/" and revised comments.

Possibly related PRs

Suggested labels

wren-ai-service

Poem

🐇
In the warren of config files I hop,
Swapping "openai/" for "lm_studio/" on top.
Models and embedders, prefixes anew,
YAML lines tidy, their meanings true.
With every small change, I twitch my nose—
For tidy configs make code that glows!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6fa60b6 and b9e8dc0.

📒 Files selected for processing (1)
  • wren-ai-service/docs/config_examples/config.lm_studio.yaml (2 hunks)
🔇 Additional comments (2)
wren-ai-service/docs/config_examples/config.lm_studio.yaml (2)

13-13: Correct LLM model prefix for LM Studio.

The model identifier has been updated from the “openai/…” prefix to “lm_studio/…”, ensuring it matches LM Studio’s naming convention and will be recognized by the litellm_llm provider.


25-25: Correct embedder model prefix for LM Studio.

The embedding model identifier has likewise been updated to use the “lm_studio/…” prefix, aligning with LM Studio’s expected format for the litellm_embedder provider.


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

@cyyeh
Copy link
Member

cyyeh commented Apr 18, 2025

@XavierMoon this is not typo. openai prefix means we use openai compatible api for lm studio. This is the rule given by litellm, which is used in wren-ai-service.

What issues are you running into actually?

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.

2 participants