3 ms·
> The Lix evaluation cache no longer caches failures, so “cached failure” is an error of the past. If this means what I think it means, I might switch to this
by snailmailman 2y ago
> The Lix evaluation cache no longer caches failures, so “cached failure” is an error of the past.
If this means what I think it means, I might switch to this from nix.
I used to occasionally get errors that would be cached in such a way that on a rerun I wouldn’t get any info. The error itself would cache but not any of the details about the error. Was super annoying cause if I lost the error details for any reason I couldn’t see them again easily. I’d have to make a pointless change somewhere and trick it into rebuilding without the cache.
- n8henrie 2y ago`--no-eval-cache`?
- snailmailman 2y agoThis flag sounds familiar. I do think it solved my problem last time. Googling a bit- it’s also unclear to me if this bug was solved in mainline Nix itself? https://github.com/NixOS/nix/issues/3872 https://github.com/NixOS/nix/issues/3872 If this Lix changelog is mostly comparing itself to Nix 2.18, I’m curious how many other changes are already in Nix 2.22. It’s kinda confusing
- nxrabl 2y agoThis seems like such a no-brainer architectural choice that it makes me wonder if there's some tradeoff I'm not seeing. Why would Nix have cached failures in the first place?
- n8henrie 2y agoIt seems to make more sense than not having them to me -- nix is all about reproducibility. If you didn't change anything, why would you get a different result? Instead of spending 15 seconds on evaluations, just tell me "you didn't change anything doofus -- cached error."