Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
OpenDAS
vllm_cscc
Commits
76df6072
Unverified
Commit
76df6072
authored
Feb 20, 2026
by
Mark McLoughlin
Committed by
GitHub
Feb 19, 2026
Browse files
[Core] Fix state names in pause_scheduler() (#34840)
Signed-off-by:
Mark McLoughlin
<
markmc@redhat.com
>
parent
16f24e87
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
vllm/v1/engine/core.py
vllm/v1/engine/core.py
+9
-9
No files found.
vllm/v1/engine/core.py
View file @
76df6072
...
...
@@ -1370,15 +1370,15 @@ class EngineCoreProc(EngineCore):
)
->
Future
|
None
:
"""Pause generation; behavior depends on mode.
All pause
stat
es queue new adds
. PAUSE_ABORT and PAUSE_KEEP
skip step();
PAUSE_WAIT
allows step() so in-flight requests can drain.
- ``abort``: Set PAUSE
_ABORT
, abort all requests, wait for abort
outputs to be sent (when running with output_queue),
clear caches,
then complete the returned Future.
- ``wait``: Set PAUSE
_WAIT
(queue adds, keep stepping); when drained,
set PAUSE_KEEP,
clear caches, complete the returned Future.
- ``keep``: Set PAUSE
_KEEP
; return a Future that completes when the
All pause
mod
es queue new adds
-- "abort" and "keep"
skip step();
"wait"
allows step() so in-flight requests can drain.
- ``abort``: Set PAUSE
D_NEW
, abort all requests, wait for abort
outputs to be sent (when running with output_queue),
optionally
clear caches,
then complete the returned Future.
- ``wait``: Set PAUSE
D_NEW
(queue adds, keep stepping); when drained,
optionally
clear caches,
then
complete the returned Future.
- ``keep``: Set PAUSE
D_ALL
; return a Future that completes when the
output queue is empty.
"""
if
mode
not
in
(
"keep"
,
"abort"
,
"wait"
):
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment