Fix Qwen Omni batched text post-processing#47060
Open
Sunt-ing wants to merge 1 commit into
Open
Conversation
Contributor
|
[For maintainers] Suggested jobs to run (before merge) run-slow: qwen2_5_omni, qwen3_omni_moe |
Contributor
CI recapDashboard: View test results in Grafana |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Qwen2_5OmniProcessorandQwen3OmniMoeProcessordecodedgenerated_outputs[0]for text post-processing. That is correct whengenerate()returns a tuple-like multimodal result, where the text sequences are the first element. It is wrong for text-only generation, wheregenerate()returns the full(batch, seq)tensor directly.For batched
pipeline("any-to-any")text calls, the model generates a two-row tensor but the processor decodes only the first row, so the pipeline returns one record for a two-item batch.This keeps the tuple/list path for multimodal outputs and decodes the whole tensor for text-only outputs. The regression guard covers both Omni processors.
End-to-end pipeline repro (real AnyToAnyPipeline + real Qwen3-Omni processor)
Environment:
Regression tests and repository checks also passed.
Regression tests and repository checks
Tests:
Also ran:
Code Agent Policy
Before submitting
Pull Request checks?
to it if that's the case.
Who can review?
cc @zucchini-nlp