| 13 Mar 2022 |
Zhaofeng Li | Hmm, then it should have been there. Probably some bug then | 03:17:27 |
Winter (she/her) | want me to file a proper bug report | 03:17:36 |
Zhaofeng Li | That would be great, with a small hive.nix/flake.nix that can trigger this 👍 | 03:21:23 |
| 14 Mar 2022 |
Chinchilla Washington | How can I deploy to a host with no internet access (or working name resolution)? Builds fail when the remote host tries to download from the the nixos cache. I'd like to still be able to use the cache but download it from the build machine instead of target host. | 01:34:34 |
Chinchilla Washington | * How can I deploy to a host with no internet access (or working name resolution)? Builds fail when the remote host tries to download from the the nixos cache. I'd like to still be able to use the cache but download it from the build machine instead of target host if that's reasonable. | 01:34:46 |
Zhaofeng Li | In reply to @cw:kernelpanic.cafe How can I deploy to a host with no internet access (or working name resolution)? Builds fail when the remote host tries to download from the the nixos cache. I'd like to still be able to use the cache but download it from the build machine instead of target host if that's reasonable. --no-substitutes which will probably be renamed in the future (https://github.com/zhaofengli/colmena/issues/59) | 01:36:52 |
Chinchilla Washington | In reply to @zhaofeng:zhaofeng.li
--no-substitutes which will probably be renamed in the future (https://github.com/zhaofengli/colmena/issues/59) syntaxerror ✅ 4m Activation successful
Thank you very much!
| 01:45:50 |
Chinchilla Washington | I should have asked this a long time ago. | 01:46:09 |
Buckley | I just disable the binary caches in the configs of machines with no internet. Less typing | 04:38:09 |
Chinchilla Washington | In reply to @buckley310:matrix.org I just disable the binary caches in the configs of machines with no internet. Less typing Sometimes the lack of internet isn't planned, heh | 05:42:08 |
Buckley | lol | 13:45:46 |
| 15 Mar 2022 |
Winter (she/her) | So when using buildOnTarget, what decides if the drv should be built and copied on the host or built on the target? I know most do the latter, but things such as a source folder (from a flake input) have definitely gotten copied before, so... | 19:48:55 |
| 16 Mar 2022 |
Zhaofeng Li | In reply to @winterqt:nixos.dev So when using buildOnTarget, what decides if the drv should be built and copied on the host or built on the target? I know most do the latter, but things such as a source folder (from a flake input) have definitely gotten copied before, so... Oops, missed this one. I think sources (fixed hash paths produced by addToStore or similar) are always directly copied, and because Colmena passes --include-outputs when copying the .drvs existing outputs will be copied as well | 21:23:16 |
| 17 Mar 2022 |
@github:maunium.net | [zhaofengli/colmena] xddxdd opened
issue
#65: Colmena build is stuck unless "-v" argument is present
When I run colmena build --on some-host, colmena will be stuck in the "Evaluating" step and seemingly never ends. When I run colmena build --on some-host -v (note the added -v argument), the same build continues normally and finishes within one minute.
Example output:
# Time 00:25:20
$ colmena build --on some-host
warning: Git tree '/path/to/my/nixos-config' is dirty
[INFO ] Using flake: git+file:///path/to/my/nixos-config
[INFO ] Enumerating nodes...
warning: Git tree '/path/to/my/nixos-config' is dirty
warning: Git tree '/path/to/my/nixos-config' is dirty
warning: Git tree '/path/to/my/nixos-config' is dirty
[INFO ] Selected 1 out of 13 hosts.
🕓 54s 1 running
# I pressed Ctrl-C after ~1min, but it will run forever if I didn't do that
# Time 00:26:19
$ colmena build --on some-host -v
warning: Git tree '/path/to/my/nixos-config' is dirty
[INFO ] Using flake: git+file:///path/to/my/nixos-config
[INFO ] Enumerating nodes...
warning: Git tree '/path/to/my/nixos-config' is dirty
warning: Git tree '/path/to/my/nixos-config' is dirty
warning: Git tree '/path/to/my/nixos-config' is dirty
[INFO ] Selected 1 out of 13 hosts.
some-host | Evaluating some-host
some-host | warning: Git tree '/path/to/my/nixos-config' is dirty
some-host | Evaluated some-host
some-host | Building some-host
some-host | /nix/store/xl1n3k4vbd8aa20kgs6nx10wyyzmbiij-nixos-system-some-host-22.05pre-git
some-host | Built "/nix/store/xl1n3k4vbd8aa20kgs6nx10wyyzmbiij-nixos-system-some-host-22.05pre-git"
| All done!
# Time 00:26:36, the same job is done in 20 seconds
When colmena is stuck, it seems to be waiting for a defunct nix-store process:
$ ps -aux
# ...
lantian 811648 0.1 0.0 1225260 6016 pts/1 S<l+ 00:25 0:00 colmena build --on some-host
lantian 847160 0.0 0.0 0 0 pts/1 Z<+ 00:25 0:00 [nix-store] <defunct>
Bisect shows this issue is introduced in https://github.com/zhaofengli/colmena/commit/26b2203da9a8a0f7913c61de3343430da66579b5.
I'm on latest nixos-unstable, and here's my nix-info report:
- system: `"x86_64-linux"`
- host os: `Linux 5.16.13-xanmod1-lantian, NixOS, 22.05 (Quokka)`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.8.0pre20220311_d532269`
- nixpkgs: `/etc/nix/inputs/nixpkgs`
| 05:38:05 |
@github:maunium.net | [zhaofengli/colmena] zhaofengli closed
issue
#65: Colmena build is stuck unless "-v" argument is present
| 06:34:24 |
| 20 Mar 2022 |
Winter (she/her) | I wish there was a way we could parallelize the derivation copy step for buildOnTarget, this takes ages on large upgrades >.< | 05:04:10 |
Winter (she/her) | especially with node packages 😅 | 05:04:33 |
| 21 Mar 2022 |
Zhaofeng Li | In reply to @winterqt:nixos.dev I wish there was a way we could parallelize the derivation copy step for buildOnTarget, this takes ages on large upgrades >.< I looked at it, and it appears that Nix used to be able to copy paths in parallel, but it's disabled for some reason: https://discourse.nixos.org/t/speed-up-nix-copy/15884/5 | 00:34:55 |
Zhaofeng Li | copyPaths is used by both nix copy and nix-copy-closure (through copyClosure) | 00:35:06 |
hexa | I wish I had the motivation to migrate to colmena already 😽 | 01:17:52 |
Winter (she/her) | In reply to @zhaofeng:zhaofeng.li I looked at it, and it appears that Nix used to be able to copy paths in parallel, but it's disabled for some reason: https://discourse.nixos.org/t/speed-up-nix-copy/15884/5 I'll ask around | 01:39:28 |
Winter (she/her) | Definitely interesting | 01:39:32 |
@github:maunium.net | [zhaofengli/colmena] Repo forked into winterqt/colmena | 01:46:02 |
@github:maunium.net | [zhaofengli/colmena] winterqt opened
pull request
#66: cli: add reboot command
| 01:57:33 |
@github:maunium.net | [zhaofengli/colmena] winterqt commented on
pull request
#66: cli: add reboot command | 01:58:47 |
@github:maunium.net | [zhaofengli/colmena] winterqt edited
pull request
#66: cli: add reboot command
| 02:00:24 |
Winter (she/her) | basically a draft if i'm being honest, but a good first step | 02:00:50 |
@github:maunium.net | [zhaofengli/colmena] lheckemann opened
issue
#67: Allow excluding hosts
Nixops has the convenient --exclude option that allows deploying every node except the given ones. This would be nice to have in colmena as well, particularly in combination with the tags feature.
| 07:03:53 |
| 22 Mar 2022 |
@github:maunium.net | [zhaofengli/colmena] justinas commented on
pull request
#66: cli: add reboot command | 22:27:26 |
| 23 Mar 2022 |
| pinage404 joined the room. | 21:22:30 |