-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: NixOS/nix
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: af7ffe882f2e^
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: NixOS/nix
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: e2e6a4651a73
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 13 files changed
- 1 contributor
Commits on May 17, 2021
-
Always send the realisations as JSON
Align all the worker protocol with `buildDerivation` which inlines the realisations as one opaque json blob. That way we don’t have to bother changing the remote store protocol when the definition of `Realisation` changes, as long as we keep the json backwards-compatible
Configuration menu - View commit details
-
Copy full SHA for af7ffe8 - Browse repository at this point
Copy the full SHA af7ffe8View commit details -
Add a dependencies field to DrvOutputInfo
Currently never used, nor set but will be useful shortly
Configuration menu - View commit details
-
Copy full SHA for ce41fce - Browse repository at this point
Copy the full SHA ce41fceView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0c1d9d4 - Browse repository at this point
Copy the full SHA 0c1d9d4View commit details
Commits on May 19, 2021
-
Extract a generic
computeClosure
functionMove the `closure` logic of `computeFSClosure` to its own (templated) function. That way we can reuse it for the realisations too
Configuration menu - View commit details
-
Copy full SHA for af83ce9 - Browse repository at this point
Copy the full SHA af83ce9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 51704fe - Browse repository at this point
Copy the full SHA 51704feView commit details -
Add a method to compute the closure of a realisation
Only considers the closure in term of `Realisation`, ignores all the opaque inputs. Dunno whether that’s the nicest solution, need to think it through a bit
Configuration menu - View commit details
-
Copy full SHA for 9ebdcc4 - Browse repository at this point
Copy the full SHA 9ebdcc4View commit details -
Configuration menu - View commit details
-
Copy full SHA for e6b6982 - Browse repository at this point
Copy the full SHA e6b6982View commit details -
Make
copyPaths
copy the whole realisations closureOtherwise registering the realisations on the remote side might fail as it now expects a complete closure
Configuration menu - View commit details
-
Copy full SHA for e2e6a46 - Browse repository at this point
Copy the full SHA e2e6a46View commit details
There are no files selected for viewing