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 =…

[图片] 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}

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

支持

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

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

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

话题		回复	浏览量
Translation silently truncated when JSON stream parsing breaks (no error raised) Bug ai , dynaloc	2	130	2026 年7 月 14 日
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	2	1408	2017 年3 月 16 日
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	155	2025 年7 月 10 日
AI translations errors Bug ai	10	249	2026 年5 月 10 日
Improve BAD CSRF error message when making API calls with content-type application/json Development	4	4361	2020 年9 月 14 日

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

相关话题