Skip to content

Conversation

@tastelikefeet
Copy link
Collaborator

Change Summary

Related issue number

Checklist

  • The pull request title is a good summary of the changes - it will be used in the changelog
  • Unit tests for the changes exist
  • Run pre-commit install and pre-commit run --all-files before git commit, and passed lint check.
  • Documentation reflects the changes where applicable

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @tastelikefeet, 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 refines the web UI's setup process by enhancing Python environment detection and virtual environment management in the start.sh script, allowing for better integration with existing Conda or virtual environments. Additionally, it updates the .gitignore to correctly exclude Node.js module directories, improving repository cleanliness.

Highlights

  • Gitignore Update: Added *node_modules* to the .gitignore file to prevent Node.js dependency directories from being tracked in version control.
  • Improved Python Environment Detection: The webui/start.sh script now includes more robust logic to detect an available Python interpreter (prioritizing python3 then python) and ensures it meets the minimum requirement of Python 3.10+.
  • Flexible Virtual Environment Management: The webui/start.sh script has been updated to first check for and utilize an existing VIRTUAL_ENV or CONDA_PREFIX before creating a new .venv, making it more compatible with existing development setups.

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

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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
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 introduces several improvements to the web UI startup process and project configuration. Key changes include adding node_modules to .gitignore, enhancing the Python version check to be more robust, and adding support for existing Conda and virtual environments in webui/start.sh. My review focuses on refining these changes for better stability and adherence to best practices. I've suggested a more precise pattern for .gitignore and a fix in the startup script to handle potential errors during the Python version check, ensuring the script provides clear feedback to the user in all scenarios.

if [ -z "$PYTHON_CMD" ]; then
echo -e "${RED}Error: Python 3.10 or higher is required but not found.${NC}"
echo -e "${YELLOW}Please install Python 3.10+ and try again.${NC}"
PY_VERSION=$($PYTHON_CMD -c "import sys; print(sys.version_info[:2] >= (3, 10))")
Copy link
Contributor

Choose a reason for hiding this comment

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

high

With set -e active, if the python command fails (e.g., if it's Python 2, which would cause a SyntaxError), the script will exit immediately without a user-friendly error message. To handle this gracefully, you should catch the error and ensure PY_VERSION is set to a value that will trigger the error condition, like 'False'.

Suggested change
PY_VERSION=$($PYTHON_CMD -c "import sys; print(sys.version_info[:2] >= (3, 10))")
PY_VERSION=$($PYTHON_CMD -c "import sys; print(sys.version_info[:2] >= (3, 10))" 2>/dev/null || echo "False")

nosetests.xml
coverage.xml
*.cover
*node_modules*
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The pattern *node_modules* is overly broad and may unintentionally ignore files that simply contain node_modules in their name (e.g., documentation files). The standard and safer practice is to use node_modules/, which specifically targets directories named node_modules anywhere in your project.

node_modules/

@tastelikefeet tastelikefeet merged commit 55199a9 into modelscope:main Jan 19, 2026
1 of 2 checks passed
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