Skip to content
Permalink

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
base: 9760a4cbcdd5^
Choose a base ref
...
head repository: NixOS/nix
compare: 9f20ff3f292c
Choose a head ref
  • 11 commits
  • 13 files changed
  • 1 contributor

Commits on May 19, 2021

  1. 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
    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    a841686 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'ca/json-realisations-in-worker-protocol'

    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    05dde12 View commit details
    Browse the repository at this point in the history

  3. Add a dependencies field to DrvOutputInfo 

    Currently never used, nor set but will be useful shortly
    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    3c72e34 View commit details
    Browse the repository at this point in the history

  4. Store the realisation deps on the local store

    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    cb16dad View commit details
    Browse the repository at this point in the history

  5. Merge branch 'generic-closure-function'

    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    36ebb2c View commit details
    Browse the repository at this point in the history

  6. 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
    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    9160c39 View commit details
    Browse the repository at this point in the history

  7. Properly track the drvoutput references when building

    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    be29c86 View commit details
    Browse the repository at this point in the history

  8. Make copyPaths copy the whole realisations closure 

    Otherwise registering the realisations on the remote side might fail as
it now expects a complete closure
    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    9181b20 View commit details
    Browse the repository at this point in the history

  9. Add a db migration script

    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    983a0c9 View commit details
    Browse the repository at this point in the history

  10. Merge branch 'ca/track-drvoutput-dependencies-2-le-retour' into ca/re… 

    …cursively-substitute-realisations
    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    9760a4c View commit details
    Browse the repository at this point in the history

  11. Recursively substitute the realisations 

    Make sure that whenever we substitute a realisation, we also substitute
its entire closure
    @thufschmitt
    thufschmitt committed May 19, 2021
    Copy the full SHA
    9f20ff3 View commit details
    Browse the repository at this point in the history