| 17 Aug 2022 |
Winter (she/her) | Has anyone noticed their building with buildOnTarget get slower recently, or is this just me/my network? Even with an existing copy (build then apply), the copying 0 paths... takes way longer than it has in the past/should. | 05:03:59 |
Winter (she/her) | Not sure how I'd debug this, though. | 05:04:20 |
Winter (she/her) | * Not sure how I'd debug this, though, as it's most likely a Nix issue or a networking issue... idk. | 05:44:39 |
David Arnold (blaggacao) | An eval is a transformer that enriches one data-structure with something else to emit a different datastructure that the CLI then consumes. In theory, there is nothing in the evaler that one couldn't also do directly in the target flake.
So it offloads the implementation of an interface onto the tooling when it is considered closer to the tooling domain in order to reduce boilerplate or enforce order on the origin data structure.
That enforcing of a certain order on the origin datastructure is contentions because it forces convergence outside of the tooling domain (where it was precisely deemed more appropriate). This time: not conformance to the target data structure, but to the expected input interface. | 19:23:22 |
David Arnold (blaggacao) | Actually, similar to my styx approach, I belive that Colmena, instead of working with a wrapper flake, could also make most benefit of the nix bundle interface which doesn precisely that job, is pure, and if I'm not ill-imformed, even has (or could have in future) specialized cross-flake caching support (unlike anything else). | 19:25:33 |
David Arnold (blaggacao) | * Actually, similar to my `styx` approach, I belive that Colmena, instead of working with a wrapper flake, could also make most benefit of the `nix bundle` interface which does precisely that job, is pure, and if I'm not ill-imformed, even has (or could have in future) specialized cross-flake caching support (unlike anything else). | 19:25:52 |
David Arnold (blaggacao) | The beauty, the bundler approach is inherently very swappable, since it would only replace one bundler with a fork of that same bundler. | 19:26:49 |
David Arnold (blaggacao) | Now, input schema enforcement is on the bundler (which is fine and absolutely what we want anyways).
Output schema enforcement can be placed on the bundler (and can be even provided by a flake input coming from Colmena).
So when a bundler updates the colmena output schema reference, then it would also emit appropriate errors if that new schema isn't satisfied by a target flake.
Vice-versa, the cli can do a preflight check on the bundler (nix eval targetbundled#colemna-version) and error out if compatibility cannot be guaranteed. | 19:30:25 |
David Arnold (blaggacao) | That way, either colmena CLI or the bundler itself error out on schema violations | 19:30:47 |
David Arnold (blaggacao) | * That way, either colmena CLI or the bundler itself error out on output schema violations | 19:31:00 |
| greaka joined the room. | 20:23:07 |
| 18 Aug 2022 |
tpw_rules | is the nixpkgs in the colmena meta used for all thehosts? | 19:03:38 |
tpw_rules | i'd really like to map nixosConfigurations in my flake to the colmena output but that doesn't quite seem possible | 19:05:49 |
phaer | In reply to @tpw_rules:matrix.org is the nixpkgs in the colmena meta used for all thehosts? Did you see this already? https://github.com/zhaofengli/colmena/issues/60#issuecomment-1047199551 | 21:01:19 |
| 19 Aug 2022 |
| kayla (she/they) changed their display name from kayla.fire to kayla (she/they). | 01:39:55 |
tpw_rules | i did now, thank you. it's still unclear what the meta nixpkgs is for? | 03:28:58 |
Winter (she/her) | In reply to @tpw_rules:matrix.org is the nixpkgs in the colmena meta used for all thehosts? Yes, see https://colmena.cli.rs/unstable/reference/meta.html#nixpkgs | 04:58:33 |
Winter (she/her) | Also see the one below it, which allows you to set a Nixpkgs pin per node. | 04:58:54 |
Winter (she/her) | * Also see the option below it, which allows you to set a Nixpkgs pin per node. | 04:59:00 |
| 20 Aug 2022 |
| hanemile changed their profile picture. | 15:56:46 |
Jane Jasperous | where i need to declare system to keep running colmena without --impure flag? | 17:39:31 |
Jane Jasperous | * where i need to declare system to keep running colmena 0.4.0-pre without --impure flag? | 17:40:09 |
| 21 Aug 2022 |
Winter (she/her) | In reply to @janejasperous:one.ems.host where i need to declare system to keep running colmena 0.4.0-pre without --impure flag? meta.nixpkgs = import nixpkgs { system = "..."; } | 01:43:59 |
Winter (she/her) | see https://colmena.cli.rs/unstable/tutorial/flakes.html#basic-configuration | 01:44:20 |
Jane Jasperous | In reply to @winterqt:nixos.dev
meta.nixpkgs = import nixpkgs { system = "..."; } is not working for me then | 08:40:09 |
Jane Jasperous | Redacted or Malformed Event | 08:41:26 |
Jane Jasperous | $ colmena apply --on nadaplex -v
warning: Git tree '/home/juanjop/Git/Projects/nixos-config' is dirty
[INFO ] Using flake: git+file:///home/juanjop/Git/Projects/nixos-config
[INFO ] Enumerating nodes...
error: attribute 'currentSystem' missing
at /nix/store/2hvsmg7w6yw7afn35dylzbmdf3qii34c-source/pkgs/top-level/impure.nix:17:43:
| 08:42:05 |
Jane Jasperous | * $ colmena apply --on nadaplex -v
warning: Git tree '/home/xxxxx/Git/Projects/nixos-config' is dirty
[INFO ] Using flake: git+file:///home/xxxxx/Git/Projects/nixos-config
[INFO ] Enumerating nodes...
error: attribute 'currentSystem' missing
at /nix/store/2hvsmg7w6yw7afn35dylzbmdf3qii34c-source/pkgs/top-level/impure.nix:17:43:
| 08:42:33 |
| greaka changed their display name from greaka ⚡️ to greaka . | 09:25:58 |
| 22 Aug 2022 |
| @v:meowy.tech joined the room. | 07:42:12 |