[docs] Fix doc build errors in /rest/#23033
Conversation
91c9f96 to
a9c2db9
Compare
|
ci/circleci: linux-build-and-unit-test failed (test result details). In the assumption it might be an intermittent failure I made a small change to one of the two files, squashed commits and force pushed to re-run the tests. The same test failed again (second try test details). Any suggestions? |
a9c2db9 to
6acf1d6
Compare
|
Saw ci/circleci: linux-build-and-unit-test fail yesterday and succeed today on an update in #23039 , so I undid yesterday's small change to one of the two files, squashed commits and force pushed to re-run the tests, and all tests succeeded today. |
6acf1d6 to
9e45134
Compare
|
Thanks for the review @agrawalreetika! I made the changes you suggested, and the errors did not come back. I've squashed commits and force-pushed the branch to update this PR. Please re-review when you have time. |
9e45134 to
a89464c
Compare
|
Had another failure of ci/circleci: linux-build-and-unit-test, so made a minor text change (adjusting end of line in a text paragraph in query.rst) and squashed/force-pushed again. The flaking text passed this time. Anyone interested in the details can follow the link to this morning's failed test, or the two intermittent failure results of the same tests linked to in my earlier comment. |
Description
Fix the three similar doc build errors in presto-docs/src/main/sphinx/rest/query.rst and presto-docs/src/main/sphinx/rest/task.rst.
Searching for this error, I found in Could not lex literal_block as “…”., which suggested:
However, sometimes there’s no appropriate lexer or the code snippet can’t be lexed properly. In that case, use
code-block:: text.Changed the three code blocks to
code-block:: textand the errors do not appear in the local docs build.Like #23023, I limited the scope of this PR to fixing only errors of this one type to simplify the work of the reviewer.
Motivation and Context
Builds on the doc build errors fixes in #23023, #22876, and #22985, these errors don't stop the build but they're annoying, and these are easy and low-risk fixes.
Impact
Documentation.
Test Plan
Local doc builds.
Contributor checklist
Release Notes