Skip to content

Detect HTTP worker runtime via /v1/models - #4368

Merged
un-def merged 1 commit into
masterfrom
pr_http_worker_runtime_detection
Oct 13, 2026
Merged

un-def merged 1 commit into
masterfrom
pr_http_worker_runtime_detection

Conversation

@un-def

@un-def un-def commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

Probe GET /v1/models first and dispatch on the first model's owned_by, the same way SMG detects the runtime. Until the runtime is known, what a gRPC worker, a starting worker, or an unrelated HTTP server produces (request errors, 404, bodies that are not a model list) is logged at debug level. Other status codes, vLLM HTTP workers (not supported, use gRPC), and unknown runtimes are logged as warnings.

For SGLang, fall back to the deprecated /get_server_info on 404 (SGLang < 0.5.6), and validate /server_info and gRPC server_args with pydantic models. Once the runtime is detected, every failure is a warning.

Probe GET /v1/models first and dispatch on the first model's
owned_by, the same way SMG detects the runtime. Until the runtime is
known, what a gRPC worker, a starting worker, or an unrelated HTTP
server produces (request errors, 404, bodies that are not a model
list) is logged at debug level. Other status codes, vLLM HTTP workers
(not supported, use gRPC), and unknown runtimes are logged as
warnings.

For SGLang, fall back to the deprecated /get_server_info on 404
(SGLang < 0.5.6), and validate /server_info and gRPC server_args with
pydantic models. Once the runtime is detected, every failure is a
warning.
@un-def
un-def merged commit e013999 into master Oct 13, 2026
26 checks passed
@un-def
un-def deleted the pr_http_worker_runtime_detection branch October 13, 2026 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant