Skip to content

Fix handling of encode_video output in vllm.py so each frame’s Base64#753

Closed
LiamLian0727 wants to merge 2 commits into
EvolvingLMMs-Lab:mainfrom
LiamLian0727:main
Closed

Fix handling of encode_video output in vllm.py so each frame’s Base64#753
LiamLian0727 wants to merge 2 commits into
EvolvingLMMs-Lab:mainfrom
LiamLian0727:main

Conversation

@LiamLian0727
Copy link
Copy Markdown
Contributor

@LiamLian0727 LiamLian0727 commented Jul 11, 2025

Description:

This PR addresses a bug in the VLLM model integration whereby encode_video() returns a List[str] of Base64‐encoded frames, but the caller treats it as a single string. As a result, the model receives invalid URLs like data:image/png;base64,['AAA','BBB',…].

Summary by CodeRabbit

  • Bug Fixes
    • Improved handling of image inputs to ensure all images, including those in nested lists or tuples, are correctly processed and included in message content. This prevents errors when dealing with mixed or non-nested image data.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 11, 2025

Walkthrough

The flatten method in the VLLM class was updated to handle both iterable and non-iterable elements, ensuring correct flattening of mixed nested and non-nested items. The generate_until method now uses this improved flatten method to process image inputs, ensuring all image strings are properly included in the message content.

Changes

File(s) Change Summary
lmms_eval/models/vllm.py Updated flatten to handle non-iterables; modified generate_until to use the improved flattening logic for image processing.

Poem

In code where images once nested deep,
A clever flatten now does sweep.
No tuple or list escapes its eye,
Each image string will surely fly.
The rabbit hops through code so neat—
With every fix, a bug’s defeat! 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ad31c4c and 40141aa.

📒 Files selected for processing (1)
  • lmms_eval/models/vllm.py (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
lmms_eval/models/vllm.py (1)
lmms_eval/models/qwen2_5_vl.py (1)
  • flatten (173-178)
🔇 Additional comments (2)
lmms_eval/models/vllm.py (2)

150-157: Approve the improved flatten logic.

The updated flatten method correctly handles mixed content (both iterable and non-iterable elements), which addresses the core issue described in the PR objectives. The original implementation assumed all elements were iterable, which would fail when processing single base64 strings alongside lists of base64 strings from encode_video().


208-208: Approve the fix for handling encode_video output.

The change to use self.flatten(imgs) correctly addresses the bug where encode_video() returns a list of Base64-encoded frames but the calling code treated it as a single string. This ensures all base64 strings are properly flattened before creating the image URLs, preventing invalid URL formats like data:image/png;base64,['AAA','BBB',...].

Comment thread lmms_eval/models/vllm.py
Comment on lines +153 to 156
if isinstance(i, (list, tuple)):
new_list.extend(i)
else:
new_list.append(j)
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.

⚠️ Potential issue

Critical bug: Fix undefined variable reference.

The flatten method has a critical bug on line 156 where it references j but j is not defined in the current scope. This will cause a NameError at runtime.

Apply this diff to fix the undefined variable:

 def flatten(self, input):
     new_list = []
     for i in input:
         if isinstance(i, (list, tuple)):
             new_list.extend(i)
         else:
-            new_list.append(j)
+            new_list.append(i)
     return new_list
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if isinstance(i, (list, tuple)):
new_list.extend(i)
else:
new_list.append(j)
def flatten(self, input):
new_list = []
for i in input:
if isinstance(i, (list, tuple)):
new_list.extend(i)
else:
new_list.append(i)
return new_list
🧰 Tools
🪛 Ruff (0.11.9)

156-156: Undefined name j

(F821)

🤖 Prompt for AI Agents
In lmms_eval/models/vllm.py around lines 153 to 156, the variable `j` is used
but not defined, causing a NameError. Replace the reference to `j` with `i` in
the else clause to correctly append the current element being iterated over.

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