Nix flake modules has outdated, add a test? about templ HOT 6 CLOSED

So I believe that it could be worth the extra run time (around 1 minute) for a guaranteed fresh build?

What do you think?

from templ.

I had a closer look at the actions, and it does build using Nix, but a stale entry fetched from the magic-nix-cache is used if the hash is not changed for the vendors.

from templ.

Comparing cached and un-cached actions runs on my own fork of this repo:

• First run, a normal commit: builds correctly and caches result.

• Second run, a PR changes version numbers, without updating the hash: builds using stale versions of modules fetched from the cache, passes!?

• The cache is deleted

• Third run: mysterious hash mismatch appears from nowhere as the cache can no longer be used to fetch the outdated hash!

Logs and run times:

Run 1 (no cache, first run): passed in 2m 38s

Run 2 (commit is made, action uses cache from run 1): passed in 1m 20s

Run 3 (same commit, without cache): failed in 2m 28s

from templ.

Just hit this as well on darwin-arm64.

from templ.

Nice investigation and summary @headblockhead

I was thinking about swapping to gomod2nix so that go modules are more than just a blob of "stuff". Got an example here: https://github.com/a-h/nix-gomod2nix-example

I think that might allow caching to be used, but also means that Nix derived SBOMs are useful.

from templ.

I've updated the flake.nix to use gomod2nix instead. I think that should resolve the issue. If you were able to re-test it, that would be great.

from templ.