[worker] fix: support for vllm V0 deprecation version

[HollowMan6]

What does this PR do?

Add concise overview of what this PR aims to achieve or accomplish. Reference related GitHub issues and PRs that help with the review.

Related to:

• [V0 Deprecation] Remove vllm.worker and update according imports vllm-project/vllm#25901
• [V0 Deprecation] Remove V0 sampling metadata vllm-project/vllm#25345

Now we first try to import WorkerWrapperBase from vllm.worker.worker_base, if we have an error, we append v1 there.

For compute_logits patch, we can just remove the import of SamplingMetadata, create a wrapper that accepts any arguments with *args, **kwargs, and pass them through to the original method, so that it can be more flexible and future-proof.

Checklist Before Starting

• Search for similar PRs. Paste at least one query link here: ...
• Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
  • {modules} include fsdp, megatron, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data
  • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
  • {type} is in feat, fix, refactor, chore, test
  • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
  • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

# Add code snippet or script demonstrating how to use this

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

• Read the Contribute Guide.
• Apply pre-commit checks: pre-commit install && pre-commit run --all-files --show-diff-on-failure --color=always
• Add / Update the documentation.
• Add unit or end-to-end test(s) to the CI workflow to cover all the code. If not feasible, explain why: ...
• Once your PR is ready for CI, send a message in the ci-request channel in the verl Slack workspace. (If not accessible, please try the Feishu group (飞书群).)

[gemini-code-assist]

Code Review

This pull request updates the code to support a newer version of vllm, which introduced some breaking changes related to module paths. The changes include a backward-compatible import for WorkerWrapperBase and making the compute_logits monkey-patch more robust by using *args and **kwargs. My review focuses on improving the robustness of the compatibility layer. I've suggested using a more specific exception in the import logic to prevent masking unrelated errors, which could lead to subtle bugs.

[HollowMan6]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates the code to support newer, backward-incompatible versions of the vllm library. The import for WorkerWrapperBase is now handled with a try-except block to accommodate its new location. The compute_logits monkey-patch has been made more generic by using *args and **kwargs, which increases its resilience to upstream API changes. These changes are sensible and correctly implemented to ensure compatibility. I have no further suggestions as the implementation looks solid.