| 29 Jan 2026 |
 crushing-smite | Create a virtual network interface, e.g. a bridge | 22:13:14 |
| crushing-smite | Create a wireguard connection | 22:13:22 |
| crushing-smite | Specify that bridge should connect to upstream internet only via wireguard | 22:13:46 |
| crushing-smite | Pretty nice, esp. it's very recent | 22:14:32 |
| crushing-smite | Would that serve my above request? | 22:14:38 |
 Ihar Hrachyshka | what's the use case? isolating a service in a "namespace"? | 22:15:32 |
| crushing-smite | microvms (via microvm.nix) connect to that bridge (and that's the only possibility with vfkit) for internet. could have an automatic proxy there. | 22:16:44 |
| Ihar Hrachyshka | I think the nix-darwin PR I linked doesn't go that far but maybe it's a start to build bridge management on top. | 22:17:16 |
| crushing-smite | What does it currently do though? I've skimmed through, but I lack experience to tell at a glance. | 22:19:05 |
| Ihar Hrachyshka | configure dns, ips, routes, mac address... basic connectivity. | 22:21:44 |
| Ihar Hrachyshka | Austin Horstman: fyi hydra built a new firefox-unwrapped | 23:35:45 |
| 30 Jan 2026 |
| Ihar Hrachyshka | swift fix: https://github.com/NixOS/nixpkgs/pull/485174 | 00:19:59 |
 Austin Horstman | nice, looks like devedition got cancelled :S | 00:55:37 |
| Ihar Hrachyshka | I have no idea what cancelled means. do you? does it indicate any issue in the package still? | 01:03:18 |
| Ihar Hrachyshka | the previous devedition timed out and looks like the nixpkgs revision included the hydra timeout: https://hydra.nixos.org/build/320734079 | 01:04:42 |
| Ihar Hrachyshka | * the previous devedition timed out and looks like the nixpkgs revision included the hydra timeout: https://hydra.nixos.org/build/320487707 | 01:05:22 |
| Ihar Hrachyshka | any idea why the timeout change seems to have no effect? | 01:05:56 |
| Ihar Hrachyshka | * any idea why the timeout change seems to have no effect? (the job duration is 3h) | 01:06:08 |
| Austin Horstman | No, I was confused by that when we were looking at logs the other day... | 01:07:44 |
| Ihar Hrachyshka | regardless, the default hydra timeout as per their own docs is 10h: https://github.com/NixOS/hydra/blob/8bc95a96f787eb36f29ceec773f5bf48bd121097/doc/manual/src/jobs.md?plain=1#L19 maybe it means something else than what I think it means :( | 01:13:30 |
| Austin Horstman | https://github.com/NixOS/hydra/issues/591 | 01:14:42 |
| Ihar Hrachyshka | there's also smth called max-silent-time that apparently can shoot a job if it doesn't print for a while | 01:18:57 |
| Austin Horstman | ah yeah | 01:19:21 |
| Austin Horstman | so might run into what i saw locally where it seemingly was hanging on the same stdout for hours | 01:19:39 |
| Ihar Hrachyshka | default at 2h though | 01:19:43 |
| Ihar Hrachyshka | yeah if it really hangs there without an output for that long... I haven't seen this happening though locally. | 01:20:19 |
| Austin Horstman | I had the one successful build the other day that took 10 hours and then each build after i had tried would just hang seemingly and i lost patience and killed them | 01:20:39 |
| Austin Horstman | always seems to be on that crash_helper | 01:21:21 |
| Ihar Hrachyshka | not always, I see some jobs end at libavcodec: https://hydra.nixos.org/build/319560478/log | 01:21:49 |
| Austin Horstman | oh okay | 01:22:01 |
