feat:Updated Deep Infra models

[HavenDV]

Created by Github Actions

Summary by CodeRabbit

• New Features

  • Expanded the selection of deep learning model options with new variants offering improved performance, context capabilities, and cost-effectiveness.

• Refactor

  • Streamlined the model offerings by reorganizing and renaming selections for greater clarity in user-facing model options.

[coderabbitai]

Walkthrough

The pull request refactors the DeepInfra model definitions by overhauling the enumeration of model identifiers, updating the associated metadata in the model provider, and refactoring predefined model classes. Several model entries are removed, updated, or renamed to reflect new specifications. The changes update both the identifier names and the mapping to model metadata across the codebase without altering the overall structural flow.

Changes

File Path	Change Summary
src/DeepInfra/.../DeepInfraModelIds.cs	Updated the model ID enumeration by adding new entries (DeepseekR1, DeepseekV3), replacing several existing entries (e.g. Llama3370BInstruct → DeepseekR1DistillLlama70B and vice versa), and renaming others (e.g. DeepseekR1 → DeepseekR1DistillQwen32B, DeepseekR1DistillLlama70B → Phi4).
src/DeepInfra/.../DeepInfraModelProvider.cs	Modified the Models dictionary by adding entries with updated metadata for new model IDs and removing outdated entries, ensuring consistency with the revised enumeration.
src/DeepInfra/.../Predefined/AllModels.cs	Refactored predefined model classes by renaming them and updating their associated model IDs. New classes were introduced (e.g. DeepseekR1DistillLlama70BModel, DeepseekV3Model), and several classes were renamed to align with the updated model identifiers.

Sequence Diagram(s)

Possibly related PRs

• feat:Updated Deep Infra models #155: Directly related to the modifications in the DeepInfraModelIds enumeration and the new model entries.
• feat:Updated Deep Infra models #34: Involves similar updates to the DeepInfraModelIds enumeration and closely aligns with these changes.
• feat:Updated Deep Infra models #151: Focuses on refactoring model identifiers and classes, directly relating to the enumeration changes and predefined model updates.

Suggested reviewers

• github-actions

Poem

I'm a rabbit with a joyful hop,
Code carrots crunch as changes drop.
Reorganized enums, models anew,
A fresh garden of code just for you.
With each little nibble, the logic does glow,
Happy to see the clean code grow!
🥕🐇

---

📜 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 ec84762 and 1ebef8e.

📒 Files selected for processing (3)

• src/DeepInfra/src/DeepInfraModelIds.cs (2 hunks)
• src/DeepInfra/src/DeepInfraModelProvider.cs (1 hunks)
• src/DeepInfra/src/Predefined/AllModels.cs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build and test / Build, test and publish

🔇 Additional comments (16)

src/DeepInfra/src/Predefined/AllModels.cs (7)

3-5: New model class for DeepseekR1
These lines define the DeepseekR1Model referencing its corresponding enum entry. The changes appear consistent with the base class usage and naming conventions.

---

8-10: New model class for DeepseekR1DistillLlama70B
Introduces DeepseekR1DistillLlama70BModel and properly references DeepInfraModelIds.DeepseekR1DistillLlama70B. Implementation follows the same pattern as other models, so it looks good.

---

13-15: New model class for DeepseekV3
The addition of DeepseekV3Model is in line with other defined models. No issues found.

---

23-25: Reintroduced Llama3370BInstruct model
These lines define Llama3370BInstructModel with an updated doc reference. Everything appears coherent with the underlying base class.

---

28-30: New MistralSmall24BInstruct2501 model
A straightforward addition that follows the same conventions as the other models.

---

33-35: New class for DeepseekR1DistillQwen32B
Defines DeepseekR1DistillQwen32BModel to match the corresponding enum. Code structure remains consistent.

---

38-40: Returning Phi4 model
These lines introduce Phi4Model using its enum ID. The pattern aligns well with other model classes.

src/DeepInfra/src/DeepInfraModelIds.cs (7)

10-18: Added DeepseekR1 enum entry
Documentation and metadata for the DeepseekR1 entry are well-formed and match the referencing code.

---

20-29: Added DeepseekR1DistillLlama70B enum entry
Introduces the corresponding documentation for the new distilled model. The docstring is thorough and matches usage in other files.

---

31-40: Added DeepseekV3 enum entry
Documentation references the new model and is properly formatted. No concerns noted.

---

54-62: Revised Llama3370BInstruct documentation
The updated doc block aligns with changes in the references throughout the code.

---

65-73: Added MistralSmall24BInstruct2501 enum entry
Introduces the doc and cost structure for this model. Everything is consistent with the general format.

---

76-84: Added DeepseekR1DistillQwen32B enum entry
All newly introduced properties and docstrings match the code usage in other files.

---

87-95: Revised Phi4 enum entry
Restores the Phi4 model details and doc references. Implementation is consistent with the rest of the enum.

src/DeepInfra/src/DeepInfraModelProvider.cs (2)

12-14: New provider entries for DeepseekR1, DeepseekR1DistillLlama70B, and DeepseekV3
These lines add the updated or newly introduced model metadata to the provider dictionary. The context lengths and costs appear to match the doc comments denoting per-million-token pricing.

---

16-18: Reinserting or updating provider entries
Here, Llama3370BInstruct, MistralSmall24BInstruct2501, and DeepseekR1DistillQwen32B are properly included in the dictionary with coherent metadata.

---

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

• 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. (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.