One-time build error (version 0.84.1)

[chrillek]

I run Hugo on a Debian system via ssh like so

git pull ; hugo --cleanDestinationDir --minify

which just now gave me this error after having pulled the changes from Github:

Start building sites …
hugo v0.84.1-4BD65E22+extended linux/amd64 BuildDate=2021-06-24T11:44:23Z VendorInfo=gohugoio
Total in 105055 ms
Error: Error building site: "/home/ck/source/content/photos/Verkehr in Asien/index.md:1:1": timed out initializing value. You may have a circular loop in a shortcode, or your site may have resources that take longer to build than the `timeout` limit in your Hugo config file.

Directly afterwards, I ran the script again without any error:

❯ ./deploy
Bereits aktuell.
Start building sites …
hugo v0.84.1-4BD65E22+extended linux/amd64 BuildDate=2021-06-24T11:44:23Z VendorInfo=gohugoio

                   |  DE
-------------------+-------
  Pages            |  210
  Paginator pages  |  774
  Non-page files   | 1970
  Static files     |   20
  Processed images | 8692
  Aliases          |   45
  Sitemaps         |    1
  Cleaned          |    0

Total in 7972 ms

Is that normal behaviour? I would have thought that running hugo regenerates everything and should take approximately the same time everytime. This is what had been suggested to me before:

Does hugo generate all pages or only those changed since last run?

The subject says it all: When I run hugo as the first step in my deployment (which uses rsync via ssh to a private host), does this generate all content or only those parts that changed since the last run? I’m asking because I have the impression that rsync uploads a lot more files than would be necessary if only the changes where concerned. An I’m not talking about taxonomy or pagination data, but pages I haven’t touched in weeks.

[bep]

@chrillek

would have thought that running hugo regenerates everything and should take approximately the same time everytime.

The keyword is cache. In your case it’s all of the images.

[chrillek]

So the images are generated only when necessary, i.e. when the original changed? Most of mine are JPGs that are resized and converted to WEBP.

Which is still a bit irritating, because the git pull downloaded only four new images. The rest were exactly the same as after the last pull. The main CSS changed, too, which is of course causing the HTML data to be regenerated. But the images … where, there’d be no need to, strictly speaking.

[bep]

@chrillek

So the images are generated only when necessary, i.e. when the original changed?

Yes. We rebuild an image if the original changed or if you change some image option.