Skip to content

Release/1.35 merge to master#1652

Open
tastelikefeet wants to merge 15 commits intomasterfrom
release/1.35
Open

Release/1.35 merge to master#1652
tastelikefeet wants to merge 15 commits intomasterfrom
release/1.35

Conversation

@tastelikefeet
Copy link
Copy Markdown
Collaborator

No description provided.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

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 merges the Release/1.35 branch into master, primarily focusing on updating various dependency versions and Docker image configurations. It ensures that the build environment and project metadata are aligned with the latest release, incorporating newer base images, updated Python packages, and a revised project version.

Highlights

  • Dependency Version Updates: The lmdeploy_version was updated from 0.10.1 to 0.11.0 in the Docker build script. Additionally, the default Python version for Docker images was bumped from 3.10.14 to 3.11.11.
  • Docker Base Image Updates: The CPU and GPU base image versions used in Dockerfiles were updated from 1.33.0-test to 1.34.0-test, reflecting newer underlying images.
  • New Python Package Installations: Several new Python packages, including icecream, soundfile, pybind11, and py-spy, were added to the Docker build process for installation.
  • Refactored Package Installations: The docker/install.sh script was cleaned up by removing direct pip install commands for autoawq, lmdeploy, and auto-gptq, suggesting these might now be handled differently or are no longer needed in this specific script.
  • Project Version Bump: The main project version in modelscope/version.py was updated from 2.0.0 to 1.35.0, along with an adjustment to the __release_datetime__.

🧠 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
Copy Markdown
Contributor

@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 appears to be a release merge, updating various dependency versions and Docker image configurations for release 1.35. The changes are mostly straightforward version bumps. I've found an area for improvement regarding code duplication in the image build script, which would improve maintainability.

Comment on lines +340 to +342
extra_content += """
RUN pip install --no-cache-dir -U icecream soundfile pybind11 py-spy
"""
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This logic for adding packages to extra_content is duplicated in LatestGPUImageBuilder.generate_dockerfile (lines 406-408). Since LatestGPUImageBuilder inherits from StableGPUImageBuilder, you could extract this common logic into a helper method to avoid duplication. Much of the generate_dockerfile method is duplicated between these two classes and could be refactored to improve 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.

2 participants