All of this is under zfs.nix:320 (mkIf enableZfs { which should
evaluate to false in my case.
In zfs.nix:268 services.zfs.trim = {enable defaults to true, could
that somehow cause config.systemd.timers.zpool-trim.enable default to
true as well irregardless of the check you linked above?
If you look at the actual pull requests for your nixos-version --hash and the commit that fixes this issue, you’ll see that your nixos version was merged 5 days ago, and the fix was only merged 4 days ago. I bet if you look at your local nixpkgs tree you’ll find the fix is not applied. Looks like it simply hasn’t gotten to the nixos-unstable channel yet.
If you look at the actual pull requests for your nixos-version --hash and the commit that fixes this issue, you’ll see that your nixos version was merged 5 days ago, and the fix was only merged 4 days ago. I bet if you look at your local nixpkgs tree you’ll find the fix is not applied. Looks like it simply hasn’t gotten to the nixos-unstable channel yet.
I did not even know about `nixos-version --hash’ until earlier this day
and am still lost between pull requests, commit hashes, build numbers
and what not.
The dates of the commits are not the dates they were merged to master. The commit date is the date they were originally authored, before the PR even went up.