Skip to content

Conversation

@MengqingCao
Copy link
Collaborator

@MengqingCao MengqingCao commented Jul 15, 2025

What this PR does / why we need it?

Support pipeline parallel with ray backend in V1Engine.

Fixes #1751

Does this PR introduce any user-facing change?

Users could specify ray as distributed backend when inferencing with pp

How was this patch tested?

CI passed with new added test.

@MengqingCao MengqingCao force-pushed the pp branch 2 times, most recently from fd7673f to 7bcce3f Compare July 21, 2025 03:07
@MengqingCao MengqingCao marked this pull request as ready for review July 21, 2025 12:28
@codecov
Copy link

codecov bot commented Jul 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.60%. Comparing base (33e1ea4) to head (05a1768).
⚠️ Report is 560 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1800      +/-   ##
==========================================
+ Coverage   60.25%   60.60%   +0.34%     
==========================================
  Files          73       75       +2     
  Lines        8006     8122     +116     
==========================================
+ Hits         4824     4922      +98     
- Misses       3182     3200      +18     
Flag Coverage Δ
unittests 60.60% <100.00%> (+0.34%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Signed-off-by: MengqingCao <cmq0113@163.com>
Signed-off-by: MengqingCao <cmq0113@163.com>
Comment on lines +16 to +17
ray>=2.47.1
protobuf==4.25.6
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this also fixed in dockerfile?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, I'll fix it in next pr

@Yikun
Copy link
Collaborator

Yikun commented Jul 23, 2025

Followup @MengqingCao

  1. We should also fix ray version this in dockerfile, let's do fix this in a separate PR and test the images.

  2. It's better to raise a issue on ray to resolve AttributeError: 'str' object has no attribute 'DESCRIPTOR' issue.

    ``` Process EngineCore_0: ERROR 07-22 08:04:33 [core.py:613] EngineCore failed to start. ERROR 07-22 08:04:33 [core.py:613] Traceback (most recent call last): ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/v1/engine/core.py", line 604, in run_engine_core ERROR 07-22 08:04:33 [core.py:613] engine_core = EngineCoreProc(*args, **kwargs) ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/v1/engine/core.py", line 431, in __init__ ERROR 07-22 08:04:33 [core.py:613] super().__init__(vllm_config, executor_class, log_stats, ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/v1/engine/core.py", line 77, in __init__ ERROR 07-22 08:04:33 [core.py:613] self.model_executor = executor_class(vllm_config) ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/executor/executor_base.py", line 294, in __init__ ERROR 07-22 08:04:33 [core.py:613] super().__init__(*args, **kwargs) ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/executor/executor_base.py", line 55, in __init__ ERROR 07-22 08:04:33 [core.py:613] self._init_executor() ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/v1/executor/ray_distributed_executor.py", line 47, in _init_executor ERROR 07-22 08:04:33 [core.py:613] super()._init_executor() ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/executor/ray_distributed_executor.py", line 95, in _init_executor ERROR 07-22 08:04:33 [core.py:613] initialize_ray_cluster(self.parallel_config) ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/executor/ray_utils.py", line 369, in initialize_ray_cluster ERROR 07-22 08:04:33 [core.py:613] _wait_until_pg_ready(current_placement_group) ERROR 07-22 08:04:33 [core.py:613] File "/__w/vllm-ascend/vllm-ascend/vllm-empty/vllm/executor/ray_utils.py", line 220, in _wait_until_pg_ready ERROR 07-22 08:04:33 [core.py:613] placement_group_specs = current_placement_group.bundle_specs ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/util/placement_group.py", line 105, in bundle_specs ERROR 07-22 08:04:33 [core.py:613] self._fill_bundle_cache_if_needed() ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/util/placement_group.py", line 115, in _fill_bundle_cache_if_needed ERROR 07-22 08:04:33 [core.py:613] self.bundle_cache = _get_bundle_cache(self.id) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/_private/client_mode_hook.py", line 142, in wrapper ERROR 07-22 08:04:33 [core.py:613] return func(*args, **kwargs) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/util/placement_group.py", line 140, in _get_bundle_cache ERROR 07-22 08:04:33 [core.py:613] ray._private.state.state.placement_group_table(pg_id)["bundles"].values() ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/_private/state.py", line 296, in placement_group_table ERROR 07-22 08:04:33 [core.py:613] return self._gen_placement_group_info(placement_group_info) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/_private/state.py", line 350, in _gen_placement_group_info ERROR 07-22 08:04:33 [core.py:613] "bundles": { ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/_private/state.py", line 353, in ERROR 07-22 08:04:33 [core.py:613] bundle.bundle_id.bundle_index: message_to_dict(bundle)["unitResources"] ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/ray/_private/protobuf_compat.py", line 47, in message_to_dict ERROR 07-22 08:04:33 [core.py:613] return MessageToDict(*args, **kwargs) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/google/protobuf/json_format.py", line 168, in MessageToDict ERROR 07-22 08:04:33 [core.py:613] return printer._MessageToJsonObject(message) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/google/protobuf/json_format.py", line 210, in _MessageToJsonObject ERROR 07-22 08:04:33 [core.py:613] return self._RegularMessageToJsonObject(message, js) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/google/protobuf/json_format.py", line 239, in _RegularMessageToJsonObject ERROR 07-22 08:04:33 [core.py:613] js[name] = [self._FieldToJsonObject(field, k) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/google/protobuf/json_format.py", line 239, in ERROR 07-22 08:04:33 [core.py:613] js[name] = [self._FieldToJsonObject(field, k) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/google/protobuf/json_format.py", line 279, in _FieldToJsonObject ERROR 07-22 08:04:33 [core.py:613] return self._MessageToJsonObject(value) ERROR 07-22 08:04:33 [core.py:613] File "/usr/local/python3.10.17/lib/python3.10/site-packages/google/protobuf/json_format.py", line 203, in _MessageToJsonObject ERROR 07-22 08:04:33 [core.py:613] message_descriptor = message.DESCRIPTOR ERROR 07-22 08:04:33 [core.py:613] AttributeError: 'str' object has no attribute 'DESCRIPTOR' ```
  3. Remove all version pin after ray issue resolved.

@Yikun Yikun merged commit 3aa3b46 into vllm-project:main Jul 23, 2025
25 checks passed
@Yikun
Copy link
Collaborator

Yikun commented Jul 23, 2025

Merge this consider the v1 PP test already be fixed and added the e2e test, I merge this now to avoid break V1 PP again.

cc @ganyi1996ppo @jianzs @zzzzwwjj

@wangxiyuan wangxiyuan mentioned this pull request Jul 23, 2025
45 tasks
MengqingCao added a commit to MengqingCao/vllm-ascend-fork that referenced this pull request Jul 26, 2025
  * Support pipeline parallel with ray backend in V1Engine.
  * Fixes vllm-project#1751

Signed-off-by: MengqingCao <cmq0113@163.com>
MengqingCao pushed a commit that referenced this pull request Aug 19, 2025
I would like to nominate Mengqing Cao (@MengqingCao
https://github.com/MengqingCao) as a maintainer, starting with my +1.

## Reason

Review Quality‌: She has completed [120+
reviews](https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao)
since Feb. 2025, include
[#review-3077842852](#2088 (review)),
[comment-2990074116](#1032 (comment)),
[comment-2921063723](#1013 (comment))
high quality review.

Sustained and Quality Contributions: She has Deep understanding of
‌vLLM‌ and ‌vLLM Ascend‌ codebases and solid contributions include The
vLLM contributions and help vLLM Ascend release is the main reason I
nominated her:

- vLLM: Things worth mentioning that she completed [28+ PR
contributions](https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+)
in vllm-project/vllm, especially for vLLM platform module to improve
vLLM mult hardware support. She is one of the important co-authors of
[vllm#8054](vllm-project/vllm#8054) and hardware
plugin RFC, this makes vllm-ascend plugin possible.
Community Involvement: She is also very active and involved in [60+
issues](https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao).

So I think she's a great addition to the vLLM Ascend Maintainer team.

- ✅**Review Quality‌:**

She has completed 120+ reviews since Feb. 2025.

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao,
include
#2088 (review),
#1446 (comment),
#1032 (comment),
#1013 (comment)
quality review.

- ✅**Sustained Contributions:**

99+ PR merged in vllm-project/vllm-ascend

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged

- ✅**Quality Contribution‌:**

She is one of the important co-authors of
vllm-project/vllm#8054 , this makes vllm-ascend
plugin possible.

Things worth mentioning that she complete 28+ PR contributions in
vllm-project/vllm, especially for vLLM platform module to improve vLLM
mult hardware support:

https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+.

At 2025 Q2, She also lead the [[RFC]: E2E CI test for key
features](#413) and
[[RFC]: Unit test coverage
improvement](#1298) to
help vllm ascend improve the coverage.

Her main contributions focus on the adaptation of parallel strategies
and communicator, such as
#1800,
#1856.

These contributions are sufficient to prove she has “Deep understanding
of ‌vLLM‌ and ‌vLLM Ascend‌ codebases”

- ✅**Community Involvement‌:**

Involved in 63+ issue reviewer
https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao

She led the v0.10.1 release as release manager


- vLLM version: v0.10.0
- vLLM main:
vllm-project/vllm@78dba40

Signed-off-by: Jade Zheng <zheng.shoujian@outlook.com>
wangxiaoteng888 pushed a commit to LCAIZJ/vllm-ascend that referenced this pull request Sep 25, 2025
I would like to nominate Mengqing Cao (@MengqingCao
https://github.com/MengqingCao) as a maintainer, starting with my +1.

## Reason

Review Quality‌: She has completed [120+
reviews](https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao)
since Feb. 2025, include
[#review-3077842852](vllm-project#2088 (review)),
[comment-2990074116](vllm-project#1032 (comment)),
[comment-2921063723](vllm-project#1013 (comment))
high quality review.

Sustained and Quality Contributions: She has Deep understanding of
‌vLLM‌ and ‌vLLM Ascend‌ codebases and solid contributions include The
vLLM contributions and help vLLM Ascend release is the main reason I
nominated her:

- vLLM: Things worth mentioning that she completed [28+ PR
contributions](https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+)
in vllm-project/vllm, especially for vLLM platform module to improve
vLLM mult hardware support. She is one of the important co-authors of
[vllm#8054](vllm-project/vllm#8054) and hardware
plugin RFC, this makes vllm-ascend plugin possible.
Community Involvement: She is also very active and involved in [60+
issues](https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao).

So I think she's a great addition to the vLLM Ascend Maintainer team.

- ✅**Review Quality‌:**

She has completed 120+ reviews since Feb. 2025.

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao,
include
vllm-project#2088 (review),
vllm-project#1446 (comment),
vllm-project#1032 (comment),
vllm-project#1013 (comment)
quality review.

- ✅**Sustained Contributions:**

99+ PR merged in vllm-project/vllm-ascend

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged

- ✅**Quality Contribution‌:**

She is one of the important co-authors of
vllm-project/vllm#8054 , this makes vllm-ascend
plugin possible.

Things worth mentioning that she complete 28+ PR contributions in
vllm-project/vllm, especially for vLLM platform module to improve vLLM
mult hardware support:

https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+.

At 2025 Q2, She also lead the [[RFC]: E2E CI test for key
features](vllm-project#413) and
[[RFC]: Unit test coverage
improvement](vllm-project#1298) to
help vllm ascend improve the coverage.

Her main contributions focus on the adaptation of parallel strategies
and communicator, such as
vllm-project#1800,
vllm-project#1856.

These contributions are sufficient to prove she has “Deep understanding
of ‌vLLM‌ and ‌vLLM Ascend‌ codebases”

- ✅**Community Involvement‌:**

Involved in 63+ issue reviewer
https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao

She led the v0.10.1 release as release manager


- vLLM version: v0.10.0
- vLLM main:
vllm-project/vllm@78dba40

Signed-off-by: Jade Zheng <zheng.shoujian@outlook.com>
chopper0126 pushed a commit to chopper0126/vllm-ascend that referenced this pull request Sep 26, 2025
### What this PR does / why we need it?
Support pipeline parallel with ray backend in V1Engine.

Fixes vllm-project#1751

### Does this PR introduce _any_ user-facing change?
Users could specify ray as distributed backend when inferencing with pp

### How was this patch tested?
CI passed with new added test.


- vLLM version: v0.9.2
- vLLM main:
vllm-project/vllm@32142b3

---------

Signed-off-by: MengqingCao <cmq0113@163.com>
chopper0126 pushed a commit to chopper0126/vllm-ascend that referenced this pull request Sep 26, 2025
I would like to nominate Mengqing Cao (@MengqingCao
https://github.com/MengqingCao) as a maintainer, starting with my +1.

## Reason

Review Quality‌: She has completed [120+
reviews](https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao)
since Feb. 2025, include
[#review-3077842852](vllm-project#2088 (review)),
[comment-2990074116](vllm-project#1032 (comment)),
[comment-2921063723](vllm-project#1013 (comment))
high quality review.

Sustained and Quality Contributions: She has Deep understanding of
‌vLLM‌ and ‌vLLM Ascend‌ codebases and solid contributions include The
vLLM contributions and help vLLM Ascend release is the main reason I
nominated her:

- vLLM: Things worth mentioning that she completed [28+ PR
contributions](https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+)
in vllm-project/vllm, especially for vLLM platform module to improve
vLLM mult hardware support. She is one of the important co-authors of
[vllm#8054](vllm-project/vllm#8054) and hardware
plugin RFC, this makes vllm-ascend plugin possible.
Community Involvement: She is also very active and involved in [60+
issues](https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao).

So I think she's a great addition to the vLLM Ascend Maintainer team.

- ✅**Review Quality‌:**

She has completed 120+ reviews since Feb. 2025.

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao,
include
vllm-project#2088 (review),
vllm-project#1446 (comment),
vllm-project#1032 (comment),
vllm-project#1013 (comment)
quality review.

- ✅**Sustained Contributions:**

99+ PR merged in vllm-project/vllm-ascend

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged

- ✅**Quality Contribution‌:**

She is one of the important co-authors of
vllm-project/vllm#8054 , this makes vllm-ascend
plugin possible.

Things worth mentioning that she complete 28+ PR contributions in
vllm-project/vllm, especially for vLLM platform module to improve vLLM
mult hardware support:

https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+.

At 2025 Q2, She also lead the [[RFC]: E2E CI test for key
features](vllm-project#413) and
[[RFC]: Unit test coverage
improvement](vllm-project#1298) to
help vllm ascend improve the coverage.

Her main contributions focus on the adaptation of parallel strategies
and communicator, such as
vllm-project#1800,
vllm-project#1856.

These contributions are sufficient to prove she has “Deep understanding
of ‌vLLM‌ and ‌vLLM Ascend‌ codebases”

- ✅**Community Involvement‌:**

Involved in 63+ issue reviewer
https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao

She led the v0.10.1 release as release manager


- vLLM version: v0.10.0
- vLLM main:
vllm-project/vllm@78dba40

Signed-off-by: Jade Zheng <zheng.shoujian@outlook.com>
Angazenn pushed a commit to Angazenn/vllm-ascend that referenced this pull request Oct 21, 2025
### What this PR does / why we need it?
Support pipeline parallel with ray backend in V1Engine.

Fixes vllm-project#1751

### Does this PR introduce _any_ user-facing change?
Users could specify ray as distributed backend when inferencing with pp

### How was this patch tested?
CI passed with new added test.


- vLLM version: v0.9.2
- vLLM main:
vllm-project/vllm@32142b3

---------

Signed-off-by: MengqingCao <cmq0113@163.com>
Angazenn pushed a commit to Angazenn/vllm-ascend that referenced this pull request Oct 21, 2025
I would like to nominate Mengqing Cao (@MengqingCao
https://github.com/MengqingCao) as a maintainer, starting with my +1.

## Reason

Review Quality‌: She has completed [120+
reviews](https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao)
since Feb. 2025, include
[#review-3077842852](vllm-project#2088 (review)),
[comment-2990074116](vllm-project#1032 (comment)),
[comment-2921063723](vllm-project#1013 (comment))
high quality review.

Sustained and Quality Contributions: She has Deep understanding of
‌vLLM‌ and ‌vLLM Ascend‌ codebases and solid contributions include The
vLLM contributions and help vLLM Ascend release is the main reason I
nominated her:

- vLLM: Things worth mentioning that she completed [28+ PR
contributions](https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+)
in vllm-project/vllm, especially for vLLM platform module to improve
vLLM mult hardware support. She is one of the important co-authors of
[vllm#8054](vllm-project/vllm#8054) and hardware
plugin RFC, this makes vllm-ascend plugin possible.
Community Involvement: She is also very active and involved in [60+
issues](https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao).

So I think she's a great addition to the vLLM Ascend Maintainer team.

- ✅**Review Quality‌:**

She has completed 120+ reviews since Feb. 2025.

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+is%3Aclosed+commenter%3Amengqingcao+-author%3Amengqingcao,
include
vllm-project#2088 (review),
vllm-project#1446 (comment),
vllm-project#1032 (comment),
vllm-project#1013 (comment)
quality review.

- ✅**Sustained Contributions:**

99+ PR merged in vllm-project/vllm-ascend

https://github.com/vllm-project/vllm-ascend/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged

- ✅**Quality Contribution‌:**

She is one of the important co-authors of
vllm-project/vllm#8054 , this makes vllm-ascend
plugin possible.

Things worth mentioning that she complete 28+ PR contributions in
vllm-project/vllm, especially for vLLM platform module to improve vLLM
mult hardware support:

https://github.com/vllm-project/vllm/pulls?q=is%3Apr+author%3AMengqingCao+is%3Amerged+.

At 2025 Q2, She also lead the [[RFC]: E2E CI test for key
features](vllm-project#413) and
[[RFC]: Unit test coverage
improvement](vllm-project#1298) to
help vllm ascend improve the coverage.

Her main contributions focus on the adaptation of parallel strategies
and communicator, such as
vllm-project#1800,
vllm-project#1856.

These contributions are sufficient to prove she has “Deep understanding
of ‌vLLM‌ and ‌vLLM Ascend‌ codebases”

- ✅**Community Involvement‌:**

Involved in 63+ issue reviewer
https://github.com/vllm-project/vllm-ascend/issues?q=is%3Aissue%20state%3Aclosed%20-author%3AMengqingCao%20commenter%3AMengqingCao

She led the v0.10.1 release as release manager


- vLLM version: v0.10.0
- vLLM main:
vllm-project/vllm@78dba40

Signed-off-by: Jade Zheng <zheng.shoujian@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: V1 pipeline parallel failed with ray backend

3 participants