zclllyybb commented on issue #3924:
URL: https://github.com/apache/doris-website/issues/3924#issuecomment-4666021703

   Breakwater-GitHub-Analysis-Slot: slot_b54b25d84b7f
   
   Initial triage:
   
   This looks like a documentation rendering regression on the 4.x `CREATE 
FUNCTION` page, not a Doris runtime issue. I can reproduce it on the live zh-CN 
page: after the Python UDF example reaches `AS $$`, the Python body is rendered 
outside the SQL code block, and the following content is wrapped in a KaTeX 
parse-error span. That matches the large red literal Markdown/SQL block shown 
in the screenshot.
   
   The source problem appears to be the indentation of the new `py_uuid_token` 
examples added by public PR apache/doris-website#3909. In 
`i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/function/CREATE-FUNCTION.md`,
 list item 6 contains fenced code blocks indented under the ordered list, but 
the embedded Python lines and closing `$$;` are not indented with the 
surrounding fenced block. The relevant areas are around lines 152-155 and 
192-195. The same pattern is also present in the zh-CN current copy and in the 
English 4.x/current copies.
   
   Suggested next step:
   
   - Fix the Markdown formatting by keeping the Python body and `$$;` inside 
the nested fenced SQL block, for example by indenting those lines consistently 
with the surrounding SQL block, or by splitting the example into a format that 
MDX will not interpret as math.
   - Rebuild or preview the docs page and verify there is no `katex-error` span 
and that the "Correct result" / "Incorrect result" sections render as normal 
text/code blocks.
   - No Doris FE/BE logs or query profiles are needed for this issue unless 
there is a separate claim that the example result itself is incorrect.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to