[BugFix] Fix async engine running on ray

[esmeetu]

A parameter is missing: use_ray_compiled_dag in RayGPUExecutorAsync after merging #3191.

@zhuohan123 Could you help test this whether is ok when use_ray_compiled_dag=True, please. Because that feature doesn't work on my machine. It seems a DevelopAPI in ray.

[cadedaniel]

cc @rkooo567

[rkooo567]

The feature is under active development. It should work though (you may need more than certain version of ray).

Btw, it is surprising this wasn't caught by any CI. Do we have tests for async engines?

[zhuohan123]

The feature is under active development. It should work though (you may need more than certain version of ray).

Btw, it is surprising this wasn't caught by any CI. Do we have tests for async engines?

This thing hits a strange corner case. It will only be wrong when we run async engines distributedly with ray. We should add a test on this.

[zhuohan123]

@esmeetu Let's use the simpler fix in #3371 instead?

[rkooo567]

@cadedaniel for our internal version, do we have unit test for this case? I'd love to upstream it if there is

[cadedaniel]

@rkooo567 we have https://github.com/anyscale/vllm/blob/main/tests/async_engine/test_api_server.py#L36-L45 and https://github.com/anyscale/vllm/blob/main/.buildkite/ci/run_distributed_test.sh#L18-L23, but I don't think either have ray dag enabled