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) [圖片] SamSaffron …

[圖片] 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:

[圖片] 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 do…

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：结构化输出响应不是有效的 JSON

支持

Falco (Falco) 2026年七月29日 15:00 2

那是一个警告，不是错误。

不过，鉴于大家一直对此感到担忧，我将把它的日志级别调整为 INFO

話題		回覆	觀看
Translation silently truncated when JSON stream parsing breaks (no error raised) Bug ai , dynaloc	2	209	2026年七月14日
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	2	1435	2017年三月16日
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	192	2025年七月10日
AI translations errors Bug ai	10	384	2026年五月10日
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	267	2025年九月26日

Discourse AI：结构化输出响应不是有效的 JSON

相關主題