Skip to content

[fix] add visual_infer_batch_size check #980

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

Merged
merged 1 commit into from
Jul 23, 2025
Merged

Conversation

SangChengC
Copy link
Contributor

No description provided.

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.

Summary of Changes

Hello @SangChengC, 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 introduces crucial input validation checks for visual inference configuration parameters. The primary goal is to prevent runtime errors and ensure stable operation by enforcing correct relationships between visual_dp and visual_infer_batch_size before the system proceeds with potentially invalid settings.

Highlights

  • Input Validation for Visual Data Parallelism: I've added a check to ensure that the visual_dp argument, which likely relates to visual data parallelism, is a positive integer. If visual_dp is less than or equal to zero, a ValueError is now raised.
  • Configuration Validation for Visual Inference Batch Size: I've implemented a new validation step for visual_infer_batch_size. This check ensures that visual_infer_batch_size is a positive integer and is also a perfect multiple of visual_dp. If this condition is not met, a ValueError is raised with a descriptive message, guiding users to provide compatible values.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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

@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 adds validation checks for visual_dp and visual_infer_batch_size. The new logic ensures visual_dp is a positive integer and visual_infer_batch_size is a positive multiple of visual_dp, preventing potential runtime errors.

Comment on lines +165 to +169
if args.visual_infer_batch_size // args.visual_dp < 1 or args.visual_infer_batch_size % args.visual_dp != 0:
raise ValueError(
f"visual_infer_batch_size ({args.visual_infer_batch_size}) must be "
f"a positive integer multiple of visual_dp ({args.visual_dp})"
)

Choose a reason for hiding this comment

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

medium

The error message could be improved to provide more context. Consider including the expected relationship between visual_infer_batch_size and visual_dp in the message to help users understand the requirement.

        raise ValueError(
            f"visual_infer_batch_size ({args.visual_infer_batch_size}) must be a positive integer multiple of visual_dp ({args.visual_dp})."
            f" Ensure that visual_infer_batch_size is divisible by visual_dp and that the result is at least 1."
        )

@hiworldwzj hiworldwzj merged commit 2cebd42 into main Jul 23, 2025
1 check passed
@hiworldwzj hiworldwzj deleted the fix-check-vit-bs branch July 23, 2025 09:26
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