Zola failing opaquely after 0.22.0 upgrade

Hello! I recently upgraded to Zola 0.22.0, and after figuring out all the new syntax highlighting stuff I can get a local build. Great! But then, when I try to build in GHA or Docker, I get this:

Building site...
ERROR Failed to build the site
ERROR I/O error: No such file or directory (os error 2)
ERROR Reason: No such file or directory (os error 2)

I haven’t had any luck figuring out what could be going on there. For whatever reason, setting RUST_LOG=trace doesn’t have any effect the way it does locally (macOS.) How can I get Zola to tell me what it’s trying to open and failing?

If you want to see the code for this site, it’s all available at zola fixes by BrianHicks · Pull Request #74 · bytes-zone/bytes-zone · GitHub

Hi Brian,

the problem is a lowercase “l” in your additional grammar file name in config.toml: it should be syntaxes/alloy.tmLanguage.json and not syntaxes/alloy.tmlanguage.json (“language” should be capitalized).

I don’t know how to convince Zola to provide more helpful output, but my process disables all optional refernces to files in config.toml and then re-enable one after the other, until I hit the error.

Yes, the error message could be more helpful :wink:

BTW: nice looking theme!

Oh that’s weird that the path is not mentioned, we should really move to use fs-err everywhere. In practice yeah if it works on macOS but not linux it’s probably case sensitivity related as @thomasweitzel said.

I’ve made Use fs-err everywhere · Issue #3082 · getzola/zola · GitHub to track it

yep, apfs strikes again. Thank you both!