Skip to content

Fix model_task pydantic warning and skip flashinfer on non-linux#3460

Open
xthomaswang wants to merge 1 commit intomlc-ai:mainfrom
xthomaswang:fix/pydantic-warning
Open

Fix model_task pydantic warning and skip flashinfer on non-linux#3460
xthomaswang wants to merge 1 commit intomlc-ai:mainfrom
xthomaswang:fix/pydantic-warning

Conversation

@xthomaswang
Copy link
Contributor

Summary

  • avoid the Pydantic protected namespace warning for model_task in MLCChatConfig
  • skip flashinfer-python for non-Linux editable installs (tested in macos)

Details

  • rename the internal Pydantic field to field_model_task and keep alias="model_task" so the serialized config format stays unchanged
  • add a platform marker to python/requirements.txt so editable installs on macOS do not try to resolve flashinfer-python

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's stability and cross-platform compatibility by addressing a Pydantic warning in the MLCChatConfig to ensure robust configuration handling, and by refining the dependency management to prevent installation failures of flashinfer-python on non-Linux environments.

Highlights

  • Pydantic Warning Fix: Resolved a Pydantic protected namespace warning by renaming the model_task field to field_model_task within MLCChatConfig and using an alias to maintain external API compatibility.
  • Platform-Specific Dependency: Modified requirements.txt to conditionally install flashinfer-python only on Linux systems, preventing installation issues on other platforms like macOS.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request effectively addresses two distinct issues: a Pydantic protected namespace warning and cross-platform compatibility for a dependency. The change in mlc_chat_config.py correctly renames the internal field model_task to field_model_task and uses alias="model_task" to resolve the Pydantic warning while maintaining the external API, aligning with existing patterns in the class. The modification in requirements.txt to add sys_platform == "linux" for flashinfer-python is a pragmatic solution to prevent installation issues on non-Linux systems, as described in the PR details. Both changes are well-implemented and contribute positively to the codebase's robustness and maintainability.

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.

1 participant