mirror of
https://github.com/mudler/LocalAI
synced 2026-05-24 09:28:23 +00:00
661a0c3b9d
fix(ollama): accept float-encoded integer options (num_ctx, top_k, ...) Home Assistant's Ollama integration encodes integer options as JSON floats (e.g. `"num_ctx": 8192.0`). Stdlib `json.Unmarshal` refuses to decode a number with fractional notation into an `int` field, so the entire request was rejected with HTTP 400 before reaching the backend: Unmarshal type error: expected=int, got=number 8192.0, field=options.num_ctx Add a custom `UnmarshalJSON` on `OllamaOptions` that routes the int fields (`top_k`, `num_predict`, `seed`, `repeat_last_n`, `num_ctx`) through `*json.Number`, then converts via `Int64()` with a `Float64()` fallback. Public field types are unchanged, so endpoint code is untouched. Float fields and `stop` continue to parse via the default path. Fixes #9837 Assisted-by: Claude Code:claude-opus-4-7 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> Co-authored-by: Ettore Di Giacinto <mudler@localai.io> |
||
|---|---|---|
| .. | ||
| agent_jobs.go | ||
| anthropic.go | ||
| anthropic_test.go | ||
| audio_transform.go | ||
| backend.go | ||
| diarization.go | ||
| elevenlabs.go | ||
| finetune.go | ||
| gallery-model.schema.json | ||
| jina.go | ||
| localai.go | ||
| message.go | ||
| message_test.go | ||
| ollama.go | ||
| ollama_test.go | ||
| openai.go | ||
| openresponses.go | ||
| prediction.go | ||
| quantization.go | ||
| request.go | ||
| schema_suite_test.go | ||
| tokenize.go | ||
| transcription.go | ||
| transcription_format.go | ||