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 …

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: استجابة المخرجات المنظمة ليست JSON صالح

الدعم

Falco (Falco) 29 يوليو 2026، 3:00م 2

هذا تحذير وليس خطأ.

ومع ذلك، سأقوم بتغيير مستواه إلى INFO في السجلات، لأن الناس يواصلون القلق بشأن هذه الرسائل

الموضوع		الردود	مرات العرض
Translation silently truncated when JSON stream parsing breaks (no error raised) Bug ai , dynaloc	2	128	14 يوليو 2026
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	2	1408	16 مارس 2017
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	155	10 يوليو 2025
AI translations errors Bug ai	10	249	10 مايو 2026
Improve BAD CSRF error message when making API calls with content-type application/json Development	4	4361	14 سبتمبر 2020

ذكاء الاصطناعي في Discourse: استجابة المخرجات المنظمة ليست JSON صالح

الموضوعات ذات الصلة