Hugo with asciidoctor incomplete rendering

[zkaip]

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.101.0+extended darwin/arm64 BuildDate=unknown

Does this issue reproduce with the latest release?

No.

OS

MacOS Monterey Version 12.4
Apple M1

config

markup:
  asciidocExt:
    backend: "html5"
    extensions: []
    failureLevel: "fatal"
    noHeaderOrFooter: true
    preserveTOC: false
    safeMode: "unsafe"
    sectionNumbers: false
    trace: false
    verbose: false
    workingFolderCurrent: false

asciidoctor --version

Asciidoctor 2.0.17 [https://asciidoctor.org]
Runtime Environment (ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.arm64e-darwin21]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

node_modules must has ./bin/asciidoctor

npm i @asciidoctor/core asciidoctor-pdf --save-dev

then add node script to package.json

"scripts": {
    "server": "hugo server",
},

then run the script

npm run server

Bug

if content too long, about more than 1400 lines,
the .Page.Content is only show some content, not complete rendering.

The end content is missing.

[jmooring]

I am unable to reproduce the problem with a test file (content/post/test.adoc) that contains over 2500 paragraphs.

Try it:

git clone --single-branch -b hugo-forum-topic-40417 https://github.com/jmooring/hugo-testing hugo-forum-topic-40417
cd hugo-forum-topic-40417
npm run server

hugo v0.102.3
Asciidoctor 2.0.16

[zkaip]

npm init -y
npm i @asciidoctor/core asciidoctor-pdf --save-dev

then add to the scripts of the package.json

...
"scripts": {
    "server": "hugo server",
},
...

then run

npm run server

reproduce the problem

[jmooring]

I am still unable to reproduce the problem.

$ node --version
v18.9.0

$ npm --version
8.19.1

$ asciidoctor --version
Asciidoctor 2.0.16
Runtime Environment (ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu])

$ hugo version
hugo v0.102.3-b76146b129d7caa52417f8e914fc5b9271bf56fc+extended linux/amd64

Can you create a minimal reproducible example (repository) that we can clone and test?

[zkaip]

please do that follow

git clone https://github.com/zkaip/hugo-forum-topic-40417
cd hugo-forum-topic-40417
npm install
npm run server

Then reproduce the problem

note that

[jmooring]

npm install throws errors and does not complete.

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN deprecated @fortawesome/fontawesome-common-types@0.3.0: Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
npm WARN deprecated @fortawesome/fontawesome-svg-core@1.3.0: Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
npm WARN deprecated @babel/polyfill@7.12.1: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path /home/jmooring/temp/hugo-forum-topic-40417/node_modules/puppeteer
npm ERR! command failed
npm ERR! command sh -c -- node install.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jmooring/.npm/_logs/2022-09-09T03_46_32_508Z-debug-0.log

[zkaip]

@jmooring

npm install throws errors and does not complete.

you can remove the package-lock.json then npm install

My node version is v14.17

[jmooring]

That makes no difference… npm install still throws errors. Downgraded node.js to v14.19.3 and had the same problem.

Sorry, but I can’t spend any more time on this. As stated earlier, the page is not truncated when running asciidoctor as a stand-alone application. Your problem seems to be related to running asciidoctor through node/npm.

[zkaip]

Yes, I use the stand-alone application asciidoctor to avoid this problem

[zkaip]

I circumvented the problem, but did not solve it.
But still, thank you.

[zkaip]

Invoker does not wait for all output to be written to stdout

this resolve it