json

Ollama returns 200 and loads a 4096 context when num_ctx sits outside « options »

jerome / 30 août 2026

Ollama’s /api/generate drops num_ctx and num_predict placed at the JSON root: HTTP 200, plausible answer, default 4096 context. ollama ps shows the truth.

Round trip of the int 22 through JSON: stringify writes "22", parse_string returns float 22.0, and seen.has(22) is false; coercing with int() at load restores TYPE_INT and has(22) becomes true.

Godot

Godot 4 parses every JSON number as a float, and Array.has(22) misses a stored 22.0

jerome / 18 août 2026

JSON.parse_string returns saved ints as floats, and Array.has(22) is false against 22.0 even though 22.0 == 22 is true. Coerce with int() at load time.

One request with format:json branching into three observed outcomes: thinking enabled gives an empty response with done_reason stop, a num_predict cap gives a fragment cut mid-string with done_reason length, and think:false gives valid JSON.

LLM

Ollama’s format:json constrains sampling — it does not promise you parseable JSON

jerome / 18 août 2026

A reasoning model can return an empty response under format:json; a num_predict cap can cut JSON mid-string. think:false and a 20-line repair cover both.