Alexander Bantyev 8cbf862e6f Flakes: computeLocks: pass correct LockParent when reusing oldLock ... Previously, when we were attempting to reuse the old lockfile information in the computeLocks function, we have passed the parent of the current input to the next computeLocks call. This was incorrect, since the follows are resolved relative to the parent. This caused issues when we tried to reuse oldLock but couldn't for some reason (read: mustRefetch is true), in that case the follows were resolved incorrectly. Fix this by passing the correct parent, and adding some tests to prevent this particular regression from happening again. Closes https://github.com/NixOS/nix/issues/5697		2021-12-02 12:02:34 +03:00
..
call-flake.nix	Represent 'follows' inputs explicitly in the lock file	2020-06-11 14:40:21 +02:00
config.cc	Adds an accept-flake-config flag	2021-11-12 09:50:07 -05:00
flake.cc	Flakes: computeLocks: pass correct LockParent when reusing oldLock	2021-12-02 12:02:34 +03:00
flake.hh	If we can't write a lock file, pretend the top-level flake is dirty	2021-09-15 18:31:42 +02:00
flakeref.cc	Set input parent at construction time	2021-09-21 14:07:16 +02:00
flakeref.hh	Switch comment format from '// ...' to '/* ... */' for consistency.	2020-09-28 09:37:26 -07:00
lockfile.cc	In flake lock file diffs, show the last-modified date of inputs if available	2021-08-11 19:35:28 +02:00
lockfile.hh	Capitalize JSON for consistency	2020-10-28 17:54:28 -05:00