Devon Rifkin e98b5e8b4e /api/show: default to empty model_info (#13785) ...

For `/api/show`, a fully missing `model_info` field trips up various
integrators (including a recent Android Studio integration).

The primary source of missing info tends to come from models with a
remote that are also missing other data. It seems better to me to return
an empty `model_info` than making up some other fields within
`model_info` (like saying the architecture is `remote` or something like
that). So this does slightly change `/api/show`'s behavior that possibly
someone is relying on, but it seems more important to ensure the field
is always there (from a quick sampling integrations seem to be robust to
missing fields _within_ it).

Fixes: https://github.com/ollama/ollama/issues/13783

2026-01-19 15:26:17 -08:00

..

examples

ci: restore previous linter rules (#13322)

2025-12-03 18:55:02 -08:00

client_test.go

api/client: handle non-json streaming errors (#13007)

2025-12-01 15:10:16 -08:00

client.go

x/imagegen: add naive TeaCache and FP8 quantization support (#13683)

2026-01-12 13:45:22 -08:00

types_test.go

preserve tool definition and call JSON ordering (#13525)

2026-01-05 18:03:36 -08:00

types_typescript_test.go

tools: support anyOf types

2025-08-05 16:46:24 -07:00

types.go

/api/show: default to empty model_info (#13785)

2026-01-19 15:26:17 -08:00