Same-named sub-aspects collide when delivering via provides.to-users
#670
Answered
by
sini
edoars
asked this question in
Help - Issues / Problem Solving / How To
|
Hit this in my config, where SymptomIf two unrelated aspects declare a sub-aspect with the same name, only one applies and the other is dropped. Reprotest-same-named-sub-aspects = denTest (
{
den,
tuxHm,
...
}:
{
den.hosts.x86_64-linux.igloo.users.tux = { };
den.aspects.igloo.includes = [ den.aspects.alpha den.aspects.beta ];
den.aspects.alpha = {
includes = [ den.aspects.alpha.tools ];
tools.provides.to-users.homeManager.home.sessionVariables.ALPHA = "yes";
};
den.aspects.beta = {
includes = [ den.aspects.beta.tools ];
tools.provides.to-users.homeManager.home.sessionVariables.BETA = "yes";
};
expr = {
alpha = tuxHm.home.sessionVariables.ALPHA or "<missing>";
beta = tuxHm.home.sessionVariables.BETA or "<missing>";
};
expected = {
alpha = "yes";
beta = "yes";
};
}
);Rename |
Answered by
sini
Sep 2, 2026
Replies: 1 comment 1 reply
|
mmmm sounds like the deduplication check isn't preserving the full provenance. I'll take a look. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
fixed-by: #671