| 2 Sep 2022 |
 @yuka:yuka.dev | Can any of the evaluators take advantage of the eval cache? | 21:05:54 |
 @linus:schreibt.jetzt | the eval cache requires pure evaluation, so AFAIU no currently | 21:06:19 |
| @linus:schreibt.jetzt | but I might have missed something on the development of pure evaluation | 21:06:28 |
| @linus:schreibt.jetzt | if pure evaluation is working, it should use the eval cache as well | 21:06:46 |
| @yuka:yuka.dev | colmena does use pure evaluation mode | 21:07:25 |
| @yuka:yuka.dev | but nix-instantiate as entry point, not nix build | 21:07:41 |
| @yuka:yuka.dev | nix-instantiate -E ... builtins.getFlake .... | 21:07:56 |
| @yuka:yuka.dev | * nix-instantiate -E '... builtins.getFlake ....' | 21:08:02 |
| @linus:schreibt.jetzt | aah. I don't think so then. Not sure though. | 21:08:16 |
| @yuka:yuka.dev | * nix-instantiate -E '... builtins.getFlake ....' --pure-eval. | 21:08:29 |
| @yuka:yuka.dev | options.set_pure_eval(self.path.is_flake()); | 21:09:01 |
| 3 Sep 2022 |
 @blaggacao:matrix.org | In reply to @zhaofeng:zhaofeng.li
There still need to be some kind of versioning and/or a contract, because David Arnold (blaggacao) is making a framework (std) that will emit this structure with its own logic I'm totally fine with a pre-1.0 versioning for the time being (i.e. without special care). I'm pretty used to tracing and chasing upstream changes on a commit basis in the nix ecosystem. | 02:31:36 |
| @blaggacao:matrix.org | In reply to @yuka:yuka.dev
In my flake, I now do:
outputs = { self, nixpkgs, colmena, ... }@inputs: {
colmenaEval = colmena.evalHive {
# whatever was in outputs.colmena before
};
nixosConfigurations = self.outputs.colmenaEval.nodes;
};
I'd do __colmena to be consumed by the CLI... Kind of alludes python's marking of an internal something | 02:34:16 |
| @blaggacao:matrix.org | In reply to @yuka:yuka.dev
Can any of the evaluators take advantage of the eval cache? The only thing on the horizon to make tooling CLI tooling better that itself depends on some sort of Eval output that I know of is numtide/nix-eval-cache. That's not really satisfying, thought. i'd support a builtin.evalCache key thing if that was proposed. | 02:38:43 |
|  @lara:uwu.is joined the room. | 11:35:33 |
|  @ronnypfannschmidt:matrix.org left the room. | 12:06:11 |
| 4 Sep 2022 |
| @yuka:yuka.dev | mini post advertising colmena and the --evaluator streaming option ;) | 10:42:02 |
| @yuka:yuka.dev | https://fedi.yuka.dev/notice/ANDaPgyBU74xfpDd8C | 10:42:03 |
| @yuka:yuka.dev | Redacted or Malformed Event | 13:17:37 |
| 5 Sep 2022 |
 aanderse | i can't point colmena to a flake online yet, can i?
like colmena apply --config github:aanderse/my-colmena-network/main | 19:28:10 |
| aanderse | or maybe i just want to build that into my flake as an app... 🤔 | 19:28:52 |
 Zhaofeng Li | In reply to @aanderse:nixos.dev
i can't point colmena to a flake online yet, can i?
like colmena apply --config github:aanderse/my-colmena-network/main I think you can, tried it and got a 404 error so it did try to fetch | 19:36:41 |
| Zhaofeng Li | It should work with any valid Flake URI | 19:36:51 |
| aanderse | oh stupid me i had a typo... it did work!
thanks ❤️ | 19:38:37 |
| aanderse | super cool
i can't get enough colmena! 🚀 | 19:39:25 |
| 6 Sep 2022 |
 dantefromhell | is there a good way to setup a "multi hive" colmena?
multi hive meaning multiple enviroments that are logically separate (e.g. customers) but that share common blueprints? | 12:58:51 |
| @yuka:yuka.dev | Separate them by deployment tags? | 13:02:02 |
