Home manager config in aspect included in host does not pass to user

[jadestar1864]

Not sure if this is how this is supposed to work, but this test is failing

flake.tests.bogus = {
  test-something = denTest (
    {
      den,
      lib,
      igloo, # igloo = nixosConfigurations.igloo.config
      tuxHm, # tuxHm = igloo.home-manager.users.tux
      ...
    }: {
      # replace <system> if you are reporting a bug in MacOS
      den.hosts.x86_64-linux.igloo.users.tux = {};

      den.aspects.my-aspect.homeManager.programs.git.enable = true;

      den.aspects.igloo.includes = [den.aspects.my-aspect];

      expr = tuxHm.programs.git.enable;
      expected = true;
    }
  );
};

I expected the homeManager config from my-aspect would pass the programs.git.enable = true to tux, but this fails. If this isn't intended, how should I pass a "global" homeManager config from a non-entity aspect?

[theutz]

I think what you might be looking for is the mutual provider battery that ships with den.

[theutz]

Let me know if that works for you!

[jadestar1864]

I don't think mutual providers did anything, but you inspired me to take another look at the batteries and I think den.batteries.host-aspects is what I want, or at least the test passed

[fmway]

Well, your case must be specific using mutual provider. It's inappropriate if the host can directly import homeManager without user consent. That's why mutual providers exist, they're act as a bridge between user and host to receive/send something.

[fmway]

I think den.batteries.host-aspects is what I want, or at least the test passed

Ah, I just found out about that battery

[sini]

Yes, host-aspects is likely the correct battery for the behavior you're seeking.

Users by default get their own resolution tree. For example, I use hyprland and by wife uses gnome. :)

I think a lot of us forget linux systems are meant to be multi-user at times, especially given the auto-login popularity.

[jadestar1864]

In a similar vein, I've got this failing test too, though I'm not sure if it's entirely related or not, or something funky that still needs to be worked out with policies? I know @sini was resolving the issues with hasAspect and den.lib.policy.when, which was pretty awesome. Is this an actual bug or something on my end?

flake.tests.bogus = {
  test-something = denTest (
    {
      den,
      lib,
      igloo, # igloo = nixosConfigurations.igloo.config
      tuxHm, # tuxHm = igloo.home-manager.users.tux
      ...
    }: {
      # replace <system> if you are reporting a bug in MacOS
      den.hosts.x86_64-linux.igloo.users.tux = {};

      den.schema.user.includes = [den.batteries.host-aspects];
      den.aspects.my-aspect.homeManager.programs.jujutsu.enable = true;

      den.aspects.igloo.includes = [den.aspects.my-aspect];

      den.aspect.tux.includes = [
        (den.lib.policy.when ({host, ...}: host.hasAspect den.aspects.my-aspect) {
          homeManager.programs.jujutsu.settings.git.sign-on-push = true;
        })
      ];

      expr = tuxHm.programs.jujutsu.settings.git.sign-on-push;
      expected = true;
    }
  );
};

[fmway]

      den.aspect.tux.includes = [

Seems a typo here (should be aspects)

[vic]

good catch, @fmway , we are having an strict mode in Den to avoid typos, since currently Den is freeform based, maybe search on PRs since that is still undocumented as far as I remember.

[sini]

Related: #551