2024-02-16 Nix team meeting minutes #124

thufschmitt · February 16, 2024, 2:29pm

Triage

Pluggable authentication by edolstra · Pull Request #9857 · NixOS/nix · GitHub

show Nix logo in the manual by fricklerhandwerk · Pull Request #9870 · NixOS/nix · GitHub

`nix run` pure unfree packages · Issue #9875 · NixOS/nix · GitHub

Another instance of the lack of configurability.

@tomberek will find the root issue and link it from there

fix `nix shell` and namespace nesting with diverted chroot store by moben · Pull Request #8578 · NixOS/nix · GitHub

flake-url prefetch hash differs between master and 2.19.2 due to nested submodules · Issue #10022 · NixOS/nix · GitHub

Assigned to @roberth for investigation

Going through the `regressions`-labeled issues

Trying to shrink that list

Restore `builtins.pathExists` behavior on broken symlinks by alois31 · Pull Request #9985 · NixOS/nix · GitHub

Another “better” fix on the way (but not done yet). @ericson2314 Will merge right away (modulo a few last-minute changes) and get the better fix later

Using libgit for deduplication yields drastically worse eval performance · Issue #9684 · NixOS/nix · GitHub

May be fixed, but not clear to what extent. Should run the benchmarks of Using libgit for deduplication yields drastically worse eval performance · Issue #9684 · NixOS/nix · GitHub to be sure

nix 2.16 requires meta.position to be an absolute path · Issue #8662 · NixOS/nix · GitHub

github.com/NixOS/nix

nix 2.16 requires meta.position to be an absolute path

opened 07:10PM - 07 Jul 23 UTC

closed 02:24PM - 16 Feb 24 UTC

guibou

bug regression

I'm using `meta.position` in order to allow the users of our build system to edi…t the definition of a rule using `nix edit .#ruleName`. It was working fine in nix `2.15`, but since nix `2.16` it complains about requiring an absolute path: ``` error: … while evaluating the 'meta.position' attribute of a derivation at «none»:0: (source not available) error: string 'foo/bar/baz.nix:54' doesn't represent an absolute path ``` I'm able to provide an absolute path in the value of `meta.position` using an hardcoded absolute path, but I don't know how to generate an absolute path which does not point to the nix store, e.g. `toString ./.` points to the nix store. This is a problem for us because we are extensively relying on nix to provide a build system for users which are not well used to nix and most of the time they just need to do some simple fixs, and we leveraged `nix edit` in order to open their editor on the right location. This is not possible anymore. **Steps To Reproduce** Create a `flake.nix` in directory `/foo/bar/baz` with: ```nix { description = "A very basic flake"; outputs = { self, nixpkgs }: { packages.x86_64-linux.hello = nixpkgs.legacyPackages.x86_64-linux.hello; packages.x86_64-linux.default = { meta.position = "flake.nix:9"; }; }; } ``` ```shell $ nix run --impure nixpkgs#nixUnstable -- --version nix (Nix) 2.16.1 $ nix run --impure nixpkgs#nixUnstable -- edit .#default error: … while evaluating the 'meta.position' attribute of a derivation at «none»:0: (source not available) error: string 'flake.nix:9' doesn't represent an absolute path $ nix run --impure nixpkgs#nix -- --version nix (Nix) 2.15.1 $ nix run --impure nixpkgs#nix -- edit .#default # Works fine ``` Changing the `meta.position` to `/foo/bar/baz/flake.nix` works fine in both context.

error: mounting /dev/pts: Operation not permitted · Issue #7791 · NixOS/nix · GitHub

github.com/NixOS/nix

error: mounting /dev/pts: Operation not permitted

opened 06:35AM - 08 Feb 23 UTC

xunfeng1980

bug installer regression

### Describe the bug sudo HOME=/root /nix/store/lsr79q5xqd9dv97wn87x12kzax8s8i1…s-nix-2.13.2/bin/nix-env -i /nix/store/lsr79q5xqd9dv97wn87x12kzax8s8i1s-nix-2.13.2 --show-trace installing 'nix-2.13.2' error: … while setting up the build environment error: mounting /dev/pts: Operation not permitted ### Steps To Reproduce Steps to reproduce the behavior: Ubuntu 20.04 install nix ### Expected behavior A clear and concise description of what you expected to happen. ### Screenshots If applicable, add screenshots to help explain your problem. ### Additional context Add any other context about the problem here. ### Notify maintainers  ### Metadata Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result. ```console [user@system:~]$ nix-shell -p nix-info --run "nix-info -m" output here ```

Parallel copy regression? · Issue #7019 · NixOS/nix · GitHub

github.com/NixOS/nix

Parallel copy regression?

opened 02:25PM - 09 Sep 22 UTC

closed 02:01PM - 16 Feb 24 UTC

edolstra

bug regression

**Describe the bug** All builds on packet builders on hydra.nixos.org started… hanging recently. Unfortunately I cannot log in to them to see where they are hanging, but trying to reproduce the hang from the command line produced some weird failures, e.g. ``` # nix build --extra-experimental-features nix-command -j0 --builders 'ssh://root@feb44263.packethost.net?base64-ssh-public-host-key=...&ssh-key=...' --expr 'with import <nixpkgs> {}; runCommand "foo" {} "echo bar; mkdir $out"' --impure -L foo> error: sized: unexpected end-of-file error: unexpected end-of-file error: builder for '/nix/store/91p9v43ylijycnq32994m40613jrjdr7-foo.drv' failed with exit code 1 ``` which appears to happen in `copyPaths()` (called by `build-remote`). On a hunch I reverted the recent parallel copy changes on a branch (https://github.com/edolstra/nix/commits/hydra-temp) and deployed that to hydra.nixos.org. With that, the packet builders seem to be fine (see https://hydra.nixos.org/machines). @vcunat @grahamc @thufschmitt **Expected behavior** A clear and concise description of what you expected to happen. **`nix-env --version` output** `nix (Nix) 2.11.0` TODO: figure out what Nix version is on the packet builders.

builtins.fetchGit regression in 2.4 when coming from 2.3 · Issue #5128 · NixOS/nix · GitHub

@thufschmitt: Seems to work on recent Nix versions
@roberth: should we warn about it?
Probably not

Triage

Going through the regressions-labeled issues

Going through the `regressions`-labeled issues