| 28 Feb 2025 |
| @hoilc:gitter.im left the room. | 10:30:45 |
| @enzime:nixos.dev left the room. | 15:10:50 |
| cleverca22 joined the room. | 22:30:21 |
| 1 Mar 2025 |
Gaétan Lepage | In reply to @hexa:lossy.network I just grep for nix-store processes How do you do that exactly? | 11:11:48 |
hexa | ps aux | grep nix-store | 18:12:56 |
hexa |
| 18:13:03 |
hexa | * hexa 48456 0.0 0.1 411196896 27744 ?? Ss 5:54PM 0:00.08 nix-store --serve --write
hexa 48413 0.0 0.1 411327968 28592 ?? Ss 5:53PM 0:02.04 nix-store --serve --write
| 18:13:08 |
Gaétan Lepage | Thanks! | 20:31:44 |
| Tristan Ross joined the room. | 20:32:55 |
Tristan Ross | Is there a policy when a maintainer of a Nix community project has left a project stale and it becomes unusable from breaking? https://github.com/nix-community/zon2nix is broken and there's multiple issues and PR's trying to fix it. A newer version of zig master breaks it completely to where it just doesn't work anymore. | 20:36:29 |
Tristan Ross | I tried contacting figsoda, the maintainer, about a year ago but never heard anything back. Last comment is 2 years old on this repo. | 20:41:38 |
Tristan Ross | * I tried contacting figsoda, the maintainer, about a year ago but never heard anything back. Last commit is 2 years old on this repo. | 20:44:11 |
| 2 Mar 2025 |
emily | Gaétan Lepage:
emily@darwin01 ~ % ps aux | grep nix-store
glepage 62259 0.0 0.1 411354320 28096 ?? S 3:24pm 0:00.06 nix-store --serve --write
glepage 62257 0.0 0.0 410748576 16160 ?? Ss 3:24pm 0:00.02 fish -c nix-store --serve --write
glepage 61857 0.0 0.1 411467984 27952 ?? S 3:24pm 0:00.05 nix-store --serve --write
glepage 61851 0.0 0.0 410757792 16384 ?? Ss 3:24pm 0:00.02 fish -c nix-store --serve --write
glepage 60953 0.0 0.1 411325648 27728 ?? S 3:24pm 0:00.03 nix-store --serve --write
glepage 60830 0.0 0.0 410748576 16096 ?? Ss 3:24pm 0:00.03 fish -c nix-store --serve --write
glepage 60491 0.0 0.1 411189456 27824 ?? S 3:24pm 0:00.04 nix-store --serve --write
glepage 60490 0.0 0.0 410739360 15824 ?? Ss 3:24pm 0:00.03 fish -c nix-store --serve --write
glepage 60469 0.0 0.1 411317456 27456 ?? S 3:24pm 0:00.08 nix-store --serve --write
glepage 60468 0.0 0.0 410889888 16608 ?? Ss 3:24pm 0:00.03 fish -c nix-store --serve --write
emily 77881 0.0 0.0 410593024 1104 s003 R+ 3:28pm 0:00.00 grep --color=auto nix-store
glepage 77528 0.0 0.1 411484368 28240 ?? S 3:28pm 0:00.05 nix-store --serve --write
glepage 77526 0.0 0.0 410749600 16352 ?? Ss 3:28pm 0:00.02 fish -c nix-store --serve --write
glepage 65537 0.0 0.1 411309264 27424 ?? S 3:25pm 0:00.04 nix-store --serve --write
glepage 65530 0.0 0.0 410757792 16512 ?? Ss 3:25pm 0:00.02 fish -c nix-store --serve --write
glepage 63427 0.0 0.1 411318480 27520 ?? S 3:25pm 0:00.04 nix-store --serve --write
glepage 63424 0.0 0.0 410757792 16528 ?? Ss 3:25pm 0:00.02 fish -c nix-store --serve --write
emily@darwin01 ~ % uptime
15:28 up 7 days, 15:02, 3 users, load averages: 57.52 36.63 20.93
| 15:29:04 |
emily | please stop overloading the shared builders | 15:29:42 |
| Heitor Augusto joined the room. | 22:58:42 |
| 3 Mar 2025 |
| bendanm joined the room. | 04:43:37 |
Ainz Ooal Gown | In reply to @rosscomputerguy:matrix.org Is there a policy when a maintainer of a Nix community project has left a project stale and it becomes unusable from breaking? https://github.com/nix-community/zon2nix is broken and there's multiple issues and PR's trying to fix it. A newer version of zig master breaks it completely to where it just doesn't work anymore. you could adopt it technically, and resolve the pending PRs. I'd recommend reaching out to the maintainer again and then ask Mic92 if they don't respond | 07:42:33 |
hexa | figsoda read the message and didn't reply | 08:45:19 |
zowoq | I've gave Tristan Ross permissions on the repo earlier, forgot to comment here as well, sorry. | 09:21:42 |
zowoq | * I gave Tristan Ross permissions on the repo earlier, forgot to comment here as well, sorry. | 09:21:59 |
| 4 Mar 2025 |
| lassulus changed their profile picture. | 17:48:17 |
| 5 Mar 2025 |
| sinan changed their profile picture. | 08:25:27 |
| @luxzi:matrix.org changed their profile picture. | 22:15:01 |
| @luxzi:matrix.org changed their display name from luxzi (she/they) to lily (she/they). | 22:15:08 |
| 6 Mar 2025 |
Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) | Finally decided i'd sign up for community builder access, i hate waiting for mass rebuilds to compile just so the one lousy VM test can start and tell me i broke stuff. After poking at apparmor and SDL, i was recently also poking at firefox, and well i guess being annoyed with compile times for dev testing is exactly the community builder usecase | 15:23:21 |
Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) | * Finally decided i'd sign up for community builder access, i hate waiting for mass rebuilds to compile just so the one lousy VM test can start and tell me i broke stuff. After poking at apparmor and then SDL, i was recently also poking at firefox, and well i guess being annoyed with compile times for dev testing is exactly the community builder usecase | 15:23:38 |
Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) | * Finally decided i'd try to sign up for community builder access, i hate waiting for mass rebuilds to compile just so the one lousy VM test can start and tell me i broke stuff. After poking at apparmor and then SDL, i was recently also poking at firefox, and well i guess being annoyed with compile times for dev testing is exactly the community builder usecase | 15:23:57 |
| Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) changed their display name from Grimmauld to Grimmauld (any/all). | 15:38:04 |
Roberto Abdelkader Martínez Pérez | Hey everyone, I ran into some issues with Mergify in nix-community/autofirma-nix, and after contacting their support, they found that the problem was caused by Mergify trying to access nix-ld, which it didn't have permissions for. This caused merge queues in other repositories within the org to get stuck as well.
Mergify has now pushed a fix that should allow other queues to refresh properly. If anyone else was experiencing similar issues, this might have been the cause.
Just sharing in case it helps!
| 19:17:24 |
| 7 Mar 2025 |
| Qyriad changed their display name from Qyriad to qyriad. | 16:40:46 |