[Bugfix] Fix precision error in LLaVA-NeXT feature size calculation

[DarkLight1337]

Our current calculations are done using Python floats which are in float64. In some edge cases, this may cause some inconsistency with HF's output. It seems that using float32 fixes the problem (not really sure why).

FIX #11704

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[jianghuyihei]

Our current calculations are done using Python floats which are in float64. In some edge cases, this may cause some inconsistency with HF's output. It seems that using float32 fixes the problem (not really sure why).

FIX #11704

I am very sorry. I encountered a new problem after modifying the code. When the img size is (161, 184), an error message Attempted to assign 1128 = 1128 multimodal tokens to 1080 placeholders is reported. Should I open a new issue?

[DarkLight1337]

Thanks for raising the issue! It should be fixed by #11772, please test again.