Skip to content

CI check for mudler/LocalAI#12687 (fork only, do not merge) - #1

Closed
pos-ei-don wants to merge 4 commits into
masterfrom
ci-pruefung-rm-2026-10-21
Closed

pos-ei-don wants to merge 4 commits into
masterfrom
ci-pruefung-rm-2026-10-21

Conversation

@pos-ei-don

Copy link
Copy Markdown
Owner

Fork-only CI run of the branch behind mudler#12687, with tests-apple and tests-backend-cpp removed to save minutes. Close after the run.

The Go side already forwards the request's effort as
Metadata["reasoning_effort"], but the sglang backend only read
enable_thinking: every level got the same model-level thinking_budget,
so low/medium/high produced identical reasoning.

- New model option `effort_budgets:low=…;medium=…;high=…` picks the
  budget of the request's level; unlisted levels and requests without an
  effort keep `thinking_budget`. Parsing reuses _parse_thinking_budget.
- A level listed in effort_budgets turns reasoning on for that request,
  so levels the Go side does not know cannot silently disable it.
- ApplyReasoningEffort now treats `xhigh` and `max` as thinking levels.
  Before, they left DisableReasoning unset, so with a model default of
  "off" asking for more reasoning produced none.

Signed-off-by: pos-ei-don <1822533+pos-ei-don@users.noreply.github.com>
- warn on an effort_budgets entry without a token count (high=)
- update comments: enable_thinking=false still wins over a listed level
- document that precedence in text-generation.md
- cover xhigh/max and the empty-entry warning in the tests

Signed-off-by: pos-ei-don <1822533+pos-ei-don@users.noreply.github.com>
…ad warning

- ApplyReasoningEffort keeps an operator's reasoning.disable for high, xhigh and max
- sglang: _configured_budget() feeds the strict-thinking warning; tested with
  effort_budgets alone

Signed-off-by: pos-ei-don <1822533+pos-ei-don@users.noreply.github.com>
@pos-ei-don pos-ei-don closed this Oct 14, 2026
@pos-ei-don
pos-ei-don deleted the ci-pruefung-rm-2026-10-21 branch October 14, 2026 02:38
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