I updated yesterday [1] and now there are a lot of errors in the logs: Discourse AI: structured output response was not valid JSON, falling back to best-effort parsing (311 bytes) I inspected the HTTP response and it had no issue. Then I tried the text with rails console: ... discourse(prod)> p =…

Fix is here: FIX: Preserve whitespace in streamed JSON (#42339) main ← jsonfix merged 07:31AM - 05 Aug 26 UTC (UTC) [Bild] SamSaffron …

[Bild] lilydjwg: and now there are a lot of errors in the logs: That is a warning, not an error. That said, I’m moving that to INFO log level, as people keep getting worried about these :face_exhaling:

[Bild] Falco: That is a warning, not an error. Well, technically true, but it indicates a bug in the code. The fallback works so no error is raised, but it is better to fix the source instead of moving it to INFO level to cover up, isn’t it? JSON allows line feed charaters as whitespace but …

To illustrate, the following is valid JSON: { "key": "value" } The following is an escaped one, which is invalid and causing the issue: {\u000a "key": "value"\u000a}

llama-server -hf mradermacher/Qwen3-4B-Instruct-2507-GGUF:Q4_K_M

A 4B model is going to struggle to comply, they are getting better, but this is certainly on the older side. If you are going 4B I probably would recommend something more recent … try Qwen 3.5-4B or Gemma 4 E4B.

I believe that llama.cpp forces the schema by picking only tokens that conforms to it. I also captured a response with tcpdump and checked that the returned response is valid JSON. It contained spaces and line breaks outside strings however (i.e. it is a pretty-printed JSON), and those line breaks …

Discourse AI: Strukturierte Ausgabe war kein gültiges JSON

Unterstützung

sam (Sam Saffron) 5. August 2026 um 05:27 5

Welches LLM verwenden Sie?

Thema		Antworten	Aufrufe
Translation silently truncated when JSON stream parsing breaks (no error raised) Bug ai , dynaloc	2	138	14. Juli 2026
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	2	1414	16. März 2017
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	157	10. Juli 2025
AI translations errors Bug ai	10	251	10. Mai 2026
Llm_tagger: Failed to parse JSON response for post 30871: unexpected character (after tags) at line... [parse.c:706] in '{"tags":":[" Bug automation , ai	8	209	26. September 2025

Discourse AI: Strukturierte Ausgabe war kein gültiges JSON

Verwandte Themen