2024-12-04 Nix team meeting minutes #200 🎉

Wednesday triage meeting

Attendees: @roberth @edolstra @Mic92

Triaging

`--print-build-logs|-L` ignores empty lines · Issue #11991 · NixOS/nix · GitHub

  • @Mic92, @edolstra: collapsing repeated blank lines could be a feature (ie preserve single blank lines, not all of them)

Labeled good first issue

Blake hashing support · Issue #11999 · NixOS/nix · GitHub

Approved for adding to hash.cc if tvix is happy about it

If blake hashing becomes popular Nix could also implement parallelism optimizations

Should it start as an experimental feature?

Idea approved.

inconsistent SRI hash requirements? · Issue #11996 · NixOS/nix · GitHub

@edolstra: Encountered this in Handle final handling for old lock files with improper narHash fields · NixOS/nix@5c49d0b · GitHub

Assigned to @edolstra

nix-hash prints a wrong warning · Issue #11997 · NixOS/nix · GitHub

Good first issue

Disallow writing `path` input to lock file · Issue #12004 · NixOS/nix · GitHub

The issue describes one possible cause.

Another could be path: inputs in the NixOS flake registry.

Workflow:

  1. Have NixOS
  2. Put nix.registry.<name>.flake
  3. NixOS turns that into a path: flakeref in the system registry

Possible solutions for this use case

a. @edolstra: Do not use the local registry for locking at all
b. Only allow non-path registry items to be used
- could be more confusing, because of unexpected complexity

Basically Remove the flake registry or diminish its role · Issue #7422 · NixOS/nix · GitHub

  • Ignore system and user registry in nix flake lock / update
  • Keep using system and user registry in nix build <installable>

Decision: approved as Disable system and user registry for locking · Issue #12010 · NixOS/nix · GitHub


            .
 .                                 .
           .     .
      .
  .                       .
 __
 \ \          .                          .
  \ \            .
  /  \
 / /\ \   .
/_/  \_\                         .


200th meeting celebratory lambda
15 Likes