I was just writing some assertions, and wanted to show the option defs for an attr-of an option, isolated using lib.modules.mergeAttrDefinitionsWithPrio.

However, mergeAttrDefinitionsWithPrio only includes the value and highestPrio, with no access to files, definitions, definitionsWithLocations, etc.

I came up with a proof of concept that seems to mostly work, however it's failing nix-build lib/tests/release.nix so is probably not lazy enough?

My question: is there an intended way to print definitions/locations for an attr-of-an-option and, if not, how could I improve my patch to make it PR-ready? Or is there an alternative approach I could take?

In this specific scenario, I'm wanting to showDefs a _module.args.* attr, but the concept could apply to any attrsOf or lazyAttrsOf option.

Just stumbled into this today:

The option `nodes.server.nixpkgs.overlays' is defined multiple times while it's expected to be unique.
       nixpkgs.overlays is set to read-only

Is there any reason for this? Why isn't the option just being merged?

Just stumbled into this today:

The option `nodes.server.nixpkgs.overlays' is defined multiple times while it's expected to be unique.
       nixpkgs.overlays is set to read-only

Is there any reason for this?

Just stumbled into this today:

The option `nodes.server.nixpkgs.overlays' is defined multiple times while it's expected to be unique.
       nixpkgs.overlays is set to read-only

Is there any reason for this? Why must it be read-only?

It looks like so:

pkgs.testers.runNixOSTest {
      nodes.server = {
      imports = [
        ({ config, ... }: {
          config = {
            nixpkgs.overlays = [
              (final: prev: {
                grocy = prev.grocy.overrideAttrs (f: p: {
                  patches = [
                    ../../patches/grocy.patch
                  ];
                });
              })
            ];
          };
        })
      ];
    };

};