AI is happening. The future is updating.GLM-5.3-Flash-CYBERSECURITY-W4A16
> [!IMPORTANT] > **Serving note — read before your first request (vLLM / SGLang with a reasoning parser).** > > - **`reasoning_effort` only accepts `"low"` and `"high"`.** Anything else — `medium`, `xhigh`, > `off`, or omitting it — silently resolves to **`max`**, the deepest mode. Template line: > `reasoning_effort ... in ['low','high'] else 'max'`. > - **At `max`, a small `max_tokens` returns an EMPTY reply.** The model spends the whole budget > inside ` ` and you get `finish_reason="length"` with `content=""`. In multi-turn the empty > turn poisons the history and the conversation does not recover. Measured: `max` + `max_tokens > 2000` dies from turn ~4; `max` + `6000` is clean; `low` and `high` are clean at 2000. > **It is budget exhaustion, not a loop** — sampling changes do not rescue it. > - **Do NOT pass `enable_thinking`.** This template has no such variable (only `clear_thinking` and > `reasoning_effort`). Passing it — or a top-level `reasoning_effort: "none"` — turns the parser off > while the model still thinks, dumping raw reasoning into `content`. > - **Reasoning is returned in `message.reasoning`**, not `message.reasoning_content` > (vLLM renamed the output field; the input side still accepts both). > - `clear_thinking` must be nested inside `chat_template_kwargs` — a top-level key is ignored. > > > Use `"high"` for hard tasks; if you want `max`, give it `max_tokens >= 6000`. > > > **Video and image parameters — measured, because several are accepted then silently ignored.** > > - 🔴 **`media_io_kwargs.video.fps` must stay BELOW the clip's own frame rate.** Requesting a value > at or above it makes the placeholder builder count 3x the real tokens and **kills the engine**: > `ValueError: Attempted to assign N = N multimodal tokens to 3N placeholders` -> `EngineDeadError`, > server down until restarted. Upstream: vLLM #55644 / #55647. `fps: 2` is the safe, accurate choice. > - **`max_frames` and `num_frames` are not interchangeable across builds.** On vLLM nightly > `max_frames` is honoured and `num_frames` ignored; on the older `0.1.dev*` line it is the exact > reverse. A client that sets only one silently gets full-rate sampling on the other build
> [!IMPORTANT] > **Serving note — read before your first request (vLLM / SGLang with a reasoning parser).** > > - **`reasoning_effort` only accepts `"low"` and `"high"`.** Anything else — `medium`, `xhigh`, > `off`, or omitting it — silently resolves to **`max`**, the deepest mode. Template line: > `reasoning_effort ... in ['low','high'] else 'max'`. > - **At `max`, a small `max_tokens` returns an EMPTY reply.** The model spends the whole budget > inside ` ` and you get `finish_reason="length"` with `content=""`. In multi-turn the empty > turn poisons the history and the conversation does not recover. Measured: `max` + `max_tokens > 2000` dies from turn ~4; `max` + `6000` is clean; `low` and `high` are clean at 2000. > **It is budget exhaustion, not a loop** — sampling changes do not rescue it. > - **Do NOT pass `enable_thinking`.** This template has no such variable (only `clear_thinking` and > `reasoning_effort`). Passing it — or a top-level `reasoning_effort: "none"` — turns the parser off > while the model still thinks, dumping raw reasoning into `content`. > - **Reasoning is returned in `message.reasoning`**, not `message.reasoning_content` > (vLLM renamed the output field; the input side still accepts both). > - `clear_thinking` must be nested inside `chat_template_kwargs` — a top-level key is ignored. > > > Use `"high"` for hard tasks; if you want `max`, give it `max_tokens >= 6000`. > > > **Video and image parameters — measured, because several are accepted then silently ignored.** > > - 🔴 **`media_io_kwargs.video.fps` must stay BELOW the clip's own frame rate.** Requesting a value > at or above it makes the placeholder builder count 3x the real tokens and **kills the engine**: > `ValueError: Attempted to assign N = N multimodal tokens to 3N placeholders` -> `EngineDeadError`, > server down until restarted. Upstream: vLLM #55644 / #55647. `fps: 2` is the safe, accurate choice. > - **`max_frames` and `num_frames` are not interchangeable across builds.** On vLLM nightly > `max_frames` is honoured and `num_frames` ignored; on the older `0.1.dev*` line it is the exact > reverse. A client that sets only one silently gets full-rate sampling on the other build