tvix: check generated crate2nix config on CI runs

#230
Opened by tazjin at 2022-12-12T11·05+00

We should have an extra step that checks whether the crate2nix config is up-to-date. This is difficult to do in a derivation, but should be fine using an extra step.

Suggested by flokli on cl/7538.

  1. Note that crate2nix generation is apparently unstable: https://github.com/kolloch/crate2nix/issues/260

    tazjin at 2022-12-12T11·49+00

  2. It seems it isn't anymore, or at least I didn't see this happen for a long time.

    flokli at 2023-12-06T19·45+00

  3. https://cl.tvl.fyi/c/depot/+/10194 would fix this, but it seems running crate2nix inside a derivation is not possible.

    We can keep this an extraStep that runs impurely, I'd prefer that over having to bump more FOD hashes.

    flokli at 2023-12-06T20·02+00

  4. it seems running crate2nix inside a derivation is not possible.

    Do we check that Cargo.lock is up to date?

    Because Cargo.nix is really just the same information, produced the same way, using the same network accesses, as Cargo.lock. It's just saved in a Nix-friendly format.

    So however you're solving the network access issue for the "is Cargo.lock up to date" check, you need to apply the same solution to the "is Cargo.nix up to date" check.

    amjoseph at 2023-12-07T11·08+00