Missing _internal/google_analytics_async.html?

[jmelot]

Disclaimer: I am an extremely infrequent and minor contributor and it's possible the following issue is something specific to my setup. As such, I totally understand if it's not worth anyone's time to help me debug this, please just close this issue if you'd rather not delve into it!

I had a little time and checked in on this repo for some small issue to do - saw #1008 which looked like it might be straightforward. I created a fresh clone of this repo and followed the installation instructions in CONTRIBUTE.md. When I tried to build the site though (bash site.sh build-site), I got some errors about a missing google analytics template:

[61] ./src/js/searchBlogPosts.js 4.65 KiB {3} [built]
[62] ./src/js/headerAnimation.js + 1 modules 10.7 KiB {1} [built]
     | ./src/js/headerAnimation.js 9.77 KiB [built]
     | ./src/js/utils.js 969 bytes [built]
    + 48 hidden modules

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets: 
  chunk-4.22619.js (1.53 MiB)
$ cross-env HUGO_ENV=production hugo -d ../dist -s site -v
ERROR deprecated: --verbose was deprecated in Hugo v0.114.0 and will be removed in Hugo 0.128.0. use --logLevel info
ERROR deprecated: config: languages.en.description: custom params on the language top level was deprecated in Hugo v0.112.0 and will be removed in Hugo 0.128.0. Put the value below [languages.en.params]. See https://gohugo.io/content-management/multilingual/#changes-in-hugo-01120
Start building sites … 
hugo v0.127.0+extended darwin/arm64 BuildDate=2024-06-05T10:27:59Z VendorInfo=brew

INFO  static: syncing static files to / duration 73.489041ms
INFO  build:  step process substep collect files 114 files_total 114 pages_total 55 resources_total 59 duration 824.869292ms
INFO  build:  step process duration 826.147416ms
INFO  build:  step assemble duration 949.458µs
ERROR render of "term" failed: "/Users/jmelot/code/opensource/airflow-site/landing-pages/site/layouts/taxonomy/baseof.html:23:7": execute of template failed: template: _default/list.html:23:7: executing "_default/list.html" at <partial "head.html" .>: error calling partial: execute of template failed: html/template:partials/head.html:19:12: no such template "_internal/google_analytics_async.html"
ERROR render of "section" failed: "/Users/jmelot/code/opensource/airflow-site/landing-pages/site/layouts/blog/baseof.html:23:7": execute of template failed: template: blog/list.html:23:7: executing "blog/list.html" at <partial "head.html" .>: error calling partial: execute of template failed: html/template:partials/head.html:19:12: no such template "_internal/google_analytics_async.html"
ERROR render of "page" failed: "/Users/jmelot/code/opensource/airflow-site/landing-pages/site/layouts/blog/baseof.html:23:7": execute of template failed: template: blog/single.html:23:7: executing "blog/single.html" at <partial "head.html" .>: error calling partial: execute of template failed: html/template:partials/head.html:19:12: no such template "_internal/google_analytics_async.html"
INFO  build:  step render pages 72 content 0 duration 18.518625ms
INFO  build:  step postProcess duration 8.25µs
INFO  build:  duration 845.701291ms
Total in 855 ms
Error: error building site: render: failed to render pages: render of "term" failed: "/Users/jmelot/code/opensource/airflow-site/landing-pages/site/layouts/taxonomy/baseof.html:23:7": execute of template failed: template: _default/list.html:23:7: executing "_default/list.html" at <partial "head.html" .>: error calling partial: execute of template failed: html/template:partials/head.html:19:12: no such template "_internal/google_analytics_async.html"
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[potiuk]

If you are on MacOS, yes, - you should use a docker linux container for that (see the github actions) - any improvements in the process are welcome, so if you have PR to improve it - feel free (but other than that, the issue should be closed)