[Bugfix]Change the exception thrown by call_hf_processor from RuntimeError to ValueError

[Abatom]

In our multimodal scenario, when the input image size does not match the model's requirements, the call_hf_processor function throws a RuntimeError.

In the async_llm_engine.py, the engine_step function only catches ValueError, which leads to that the client hangs and cannot exit. If the call_hf_processor function throws a ValueError instead, the client can exit normally.

In fact, an image size mismatch should be considered a ValueError.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[robertgshaw2-redhat]

In our multimodal scenario, when the input image size does not match the model's requirements, the call_hf_processor function throws a RuntimeError.

In the async_llm_engine.py, the engine_step function only catches ValueError, which leads to that the client hangs and cannot exit. If the call_hf_processor function throws a ValueError instead, the client can exit normally.

In fact, an image size mismatch should be considered a ValueError.

Does this get called inside generate() or inside output_handler_loop?

[DarkLight1337]

Thanks for fixing!

[Abatom]

Does this get called inside generate() or inside output_handler_loop?

It is called inside the run_engine_loop.