Non-deterministic Builds

Is it expected that I’d see non-deterministic builds given a config like below?

[[cascade]]
  type = "microsite"
  supTitle = "Category"
  heroClass = "bg-white pt-0"
  theme = "light"
  [cascade._target]
    path = "/{ai,ads/learn,learn,web3}/category**"

[[cascade]]
  sectionTaxonomy = "ai/category"
  bodyClass = "ai-page"
  [cascade._target]
    path = "/ai/category**"

[[cascade]]
  sectionTaxonomy = "ads/learn/category"
  bodyClass = "ads/learn-page"
  theme = "extra-light"
  [cascade._target]
    path = "/ads/learn/category**"

[[cascade]]
  sectionTaxonomy = "learn/category"
  bodyClass = "learn-page taxonomy-page"
  [cascade._target]
    path = "/learn/category**"

[[cascade]]
  sectionTaxonomy = "web3/category"
  bodyClass = "web3-page taxonomy-page"
  [cascade._target]
    path = "/web3/category**"

My expectation was that the initial block would set a baseline, and then the subsequent blocks would override that baseline config. Instead, though, it appears that some builds choose the first cascade block, and others choose the subsequent, applicaple block.

Simplified reproduction can be found here: GitHub - AlanBreck/hugo-testing at non-deterministic-cascade

See Overlapping `cascade` rules are applied in nondeterministic order · Issue #12594 · gohugoio/hugo · GitHub

1 Like

Ah, thank you.

…it also appears that 2024 me seemed to think my issue was related as well.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.