[BugFix][EC Connector] Fix EC Connector of ec_both roles (#13183)

[hanxi-java]

What this PR does / why we need it?

This PR will cause startup failure when launching the service with the argument --ec-transfer-config '{ "ec_connector": "ECExampleConnector", "ec_role": "ec_both" }'. The vLLM community has already fixed this issue via PR vllm-project/vllm#34783. This pull request ports the relevant fixes for adaptation.

This PR:

• Revised the overridden execute_model and get_kv_cache_spec methods in /vllm_ascend/worker/model_runner_v1.py. We align the processing logic under the ec_both role scenario with the official implementation from the upstream vLLM community.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

• All repository pre-commit hooks passed, including ruff, formatting, spelling, custom Python checks, and commit sign-off validation.
• Python syntax compilation passed for the modified backend.
• Targeted checks passed for protocol whitespace, comments, missing environment variables, missing-file error propagation

What this PR does / why we need it?

Does this PR introduce any user-facing change?

How was this patch tested?

• vLLM version: v0.26.0
• vLLM main: vllm-project/vllm@d02df74

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a startup failure encountered when using the 'ec_both' role in the EC Connector. By adjusting the conditional checks for EC transfer roles to align with upstream vLLM logic, the connector now correctly handles data dumping and KV cache specifications, ensuring stability during service initialization.

Highlights

• EC Connector Logic Fix: Updated the logic for the 'ec_both' role in the EC Connector to correctly handle producer/consumer status, preventing startup failures.
• Upstream Alignment: Aligned the processing logic in 'execute_model' and 'get_kv_cache_spec' with the official vLLM upstream implementation.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

Suggested PR Title:

[Worker][BugFix] Update EC transfer check to exclude consumer instead of strictly requiring producer

Suggested PR Summary:

### What this PR does / why we need it?
This PR updates the condition checks in `vllm_ascend/worker/model_runner_v1.py` where `has_ec_transfer()` is used. Specifically, it changes the check from `get_ec_transfer().is_producer` to `not get_ec_transfer().is_consumer` in both `execute_model` and `get_kv_cache_spec`. This ensures that any non-consumer transfer state is handled correctly.

### Does this PR introduce _any_ user-facing change?
No user-facing changes are introduced.

### How was this patch tested?
No new tests were added. Existing tests should be run to verify the behavior.

I have no further feedback as there are no review comments to evaluate.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

---

Tip

💡 Consider Linking a Related Issue or RFC

Your PR title contains the [BugFix] tag, indicating a bug fix or new feature.

Linking a related issue or RFC in the PR description is strongly encouraged — it gives reviewers helpful context and speeds up the review. You can use any of these keywords:

• Fixes #<issue_number>
• Closes #<issue_number>
• Resolves #<issue_number>
• Refs #<rfc_or_issue_number> (for RFCs)

🙏 Thanks for helping us keep the project well-organized!

[hanxi-java]

/rerun