[Feature] Support Omni serving abort request

[ZeldaHuang]

PLEASE FILL IN THE PR DESCRIPTION HERE ENSURING ALL CHECKLIST ITEMS (AT THE BOTTOM) HAVE BEEN CONSIDERED.

Purpose

ref #419
Changes:

• Add OmniStageTaskType indicate the different task send to stage's in_q, for now there are three task types : SHUTDOWN、GENERATE、ABORT
• Add abort interface to AsyncOmni. If the user cancels generation on the client side, we will catch the GeneratorExit error and submit an abort task to all stages.

Test Plan

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft.

BEFORE SUBMITTING, PLEASE READ https://github.com/vllm-project/vllm-omni/blob/main/CONTRIBUTING.md (anything written below this line will be removed by GitHub Actions)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[hsliuustc0106]

please resolve conflicts after #391 merged

[ZeldaHuang]

please resolve conflicts after #391 merged

@hsliuustc0106 Done

[hsliuustc0106]

fix ci please

[hsliuustc0106]

@yinpeiqi PTAL

[yinpeiqi]

lgtm. Do we need test case for abort operation?

[hsliuustc0106]

• resolve conflicts since [Refactor] let the AsyncOmni class inherit from Omni class #511 merged
• add CI tests for abort request

[ZeldaHuang]

@hsliuustc0106 add test_async_omni.py , please review

[hsliuustc0106]

@yinpeiqi PTAL for the asyncomni

[hsliuustc0106]

[2025-12-30T12:14:22Z] WARNING 12-30 12:14:22 [omni.py:292] [AsyncOrchestrator] Initialization timeout: only 0/1 stages are ready; not ready: [0].

it seems the timeout problem, how long do you wait for the engine initializaiton

for the current online case:

        # Wait for server to be ready
        max_wait = 600  # 10 minutes
        start_time = time.time()
        while time.time() - start_time < max_wait:
            try:
                with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock:
                    sock.settimeout(1)
                    result = sock.connect_ex((self.host, self.port))
                    if result == 0:
                        print(f"Server ready on {self.host}:{self.port}")
                        return
            except Exception:
                pass
            time.sleep(2)

        raise RuntimeError(f"Server failed to start within {max_wait} seconds")

[ZeldaHuang]

@hsliuustc0106 It seems that simple unit test only has cpu environment, move asyn_comni test to e2e test

[hsliuustc0106]

@hsliuustc0106 It seems that simple unit test only has cpu environment, move asyn_comni test to e2e test

ORZ, I just realized it.