Robert Hensing

Instead of the latest job, it should perhaps be the latest change in each attribute. (maybe that's what you meant? job is different in, say, hydra) That will work better...

I'm glad you've described both problems, because since this week, you can solve the asynchronous build directly with the new `onSchedule` job feature. While adding the `.git` may make your...

Where it says ` herculesCI = { ... }: {`, you can ask for the [git revision](https://docs.hercules-ci.com/hercules-ci-agent/evaluation/#params-herculesCI-commit), ` herculesCI = { rev, ... }: {`, and add that to the...

A workaround for this, when using a `ci.nix`, is to start the file with: ``` args@{ src ? { ref = null; }, submodulesFetched ? builtins.pathExists ./some/path/inside/submodule, ... }: #...

`secrets.json` is intentionally a mutable file, so checking it at startup is not a guarantee that it will keep working. "Strictness" like that is a double-edged sword. It can help...

This seems to now cause a failure in the daemon compatibility test in https://github.com/NixOS/nix/pull/9546. Could you have a look @Ericson2314?

The logic should also apply to CA realisation (`.doi`) lookups, which are currently just drvHash based; not only input addressed derivation outputs seem to suffer from the discrepancy.

Probably best to start with - https://github.com/NixOS/nix/issues/9189 That will give us the language to describe the new hashing scheme more effectively.

Blocked on - [ ] Backport of https://github.com/NixOS/nixpkgs/pull/282886 - [ ] #9546

> Another heuristic is whether the frame has `addErrorContext`. IMO this would be very very important to include for NixOS usability. The team has [approved](https://github.com/NixOS/nix/issues?q=is%3Aopen+is%3Aissue+label%3A%22idea+approved%22) this one in https://github.com/NixOS/nix/issues/7553, ~so...