Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Error: Error building site: failed to render pages: render of "page" failed

See original GitHub issue

Describe the bug

I was trying to build the example website. I created a new site, cloned the repo, and copied everything from E:\IMZLUO\themes\DoIt\exampleSite to E:\IMZLUO\.

Expected behavior

The example site should have been built successfully.

Screenshots

E:\IMZLUO>hugo serve --disableFastRender
Start building sites …
hugo v0.84.4-020E4ACE+extended windows/amd64 BuildDate=2021-07-01T11:51:55Z VendorInfo=gohugoio
WARN 2021/07/04 00:09:35

Current environment is "development". The "comment system", "PWA", "CDN" and "fingerprint" will be disabled.
当前运行环境是 "development". "评论系统", "PWA", "CDN" 和 "fingerprint" 不会启用.
Built in 30626 ms
Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: posts/single.html:122:124: executing "content" at <partial "function/content.html">: error calling partial: "E:\IMZLUO\themes\DoIt\layouts\partials\function\content.html:6:23": execute of template failed: template: partials/function/content.html:6:23: executing "partials/function/content.html" at <partial "function/ruby.html" $content>: error calling partial: partial that returns a value needs a non-zero argument.

Build Environment

OS: Windows 10
Theme version/commit: ee866f9
Hugo version: v0.84.4-020E4ACE+extended

Preview Environment

N/A

Additional Information

N/A

Issue Analytics

State:
Created 2 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

2reactions

HEIGE-PCloudcommented, Jul 4, 2021

The built-in shortcode tweet is causing problem again. The timeout is caused by failing in Twitter’s API.

Remove the line {{< tweet 877500564405444608 >}} in the following 4 files and try build the site again.

DoIt\exampleSite\content\posts\tests\builtin-shortcodes-tests\index.en.md Line 48
DoIt\exampleSite\content\posts\theme-documentation-built-in-shortcodes\index.en.md Line 138
DoIt\exampleSite\content\posts\theme-documentation-built-in-shortcodes\index.fr.md Line 157
DoIt\exampleSite\content\posts\theme-documentation-built-in-shortcodes\index.zh-cn.md Line 139

If you remove ignoreErrors = ["error-remote-getjson"] in your config file, you should see the error log for Twitter.

1reaction

zhaoyiluocommented, Jul 4, 2021

The twitter ghost is really annoying.

I tried one more time on my company computer and all the issues related to Twitter disappeared (even no need to include ignoreErrors = ["error-remote-getjson"]).

Maybe I should transfer all my work from my personal laptop to avoid these unnecessary issues.

BTW, thanks for your timely fix and everything is set now!