| 22 Jul 2024 |
 K900 | e.g. | 12:40:43 |
 Clumsily6239 | Awesome, thank you. | 12:41:35 |
| 23 Jul 2024 |
 zowoq | https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps
The rate limit for GitHub Apps using an installation access token scales with the number of repositories and number of organization users. Conversely, OAuth apps have lower rate limits and do not scale.
Maybe the size of nix-community means the rate limits aren't a problem.
| 01:05:52 |
| zowoq | I checked stable and it seems to use a lot less memory than it was on main so I've enabled buildbot again. | 01:06:07 |
 Gaétan Lepage | Thanks a lot zowoq ! | 06:05:01 |
|  Ezzobir Bezziou joined the room. | 08:23:46 |
 emily | does the community builder push things to a binary cache? | 08:33:24 |
| zowoq | No, only the CI builds are pushed to the cache. | 09:08:25 |
| emily | gotcha | 09:33:31 |
| emily | I guess there's nothing stopping you using Cachix yourself on the builder to push to your own cache | 09:33:54 |
 Mic92 | @emilazy:matrix.org: with so many trusted users the binary cache would become a bit dodgy. | 11:19:08 |
| emily | indeed | 11:19:30 |
| emily | my use-case is transporting this digiKam build into a throwaway VM to test it :) | 11:19:41 |
| emily | but I'll just nix-copy-closure | 11:19:49 |
| Mic92 | It's cooler if we don't need to trust everyone as much and instead provide access more freely | 11:20:02 |
| emily | (I don't even set the community builder as a remote builder, I just SSH in to build stuff) | 11:20:30 |
| emily | thanks again for all the work running these builders btw, and sorry for building multiple WebKits lately :) | 11:21:18 |
| Mic92 | nix-fast-build can automate the copy also. But unsure if it fits your workflow | 11:21:26 |
| Mic92 | It's nice to see machines are not just idle | 11:21:49 |
| emily | I've been doing a lot of treewide sweeps lately, so I can use up all the idle cycles in the world :) | 11:22:34 |
| emily | I haven't looked at nix-fast-build yet, but it looks really nice. the problem is just that I don't want to put builds from the community builder in my main store | 11:23:09 |
| emily | aha, but maybe I could use --copy-to | 11:24:06 |
| emily | oh, or --no-download :) | 11:24:35 |
| emily | thanks for the pointer, I'll have to investigate this further as it'll probably be nicer than repeatedly git pulling a Nixpkgs clone on the builder. | 11:24:45 |
| emily | is there any way to get nixpkgs-review to use it? | 11:24:53 |
| Mic92 | Mhm maybe but unsure where nix-shell would than run | 11:25:47 |
| Mic92 | I think we should just have a nixpkgs clone on the machine | 11:26:42 |
| emily | I've already done the initial clone so it wouldn't speed up bumping my branches, but yeah it'd be nice to --reference it | 11:27:48 |
| emily | the aarch64 box has that: https://github.com/NixOS/aarch64-build-box?tab=readme-ov-file#faster-nixpkgs-clone | 11:27:53 |
| emily | would be nice to have the same interface maybe | 11:28:21 |
