| 10 Jul 2025 |
 Arian | if I'm reading the bill right we currently spend 570 dollars per month on GET requests and only 60 dollars per month on PUT
PUT is charged | 19:08:55 |
| Arian | * if I'm reading the bill right we currently spend 570 dollars per month on GET requests and only 60 dollars per month on PUT
| 19:09:10 |
| Arian | okay so seems not caching 404s is kind of a "feature" | 19:14:14 |
| Arian | because it means we don't need to do cache-busting on channel bumps | 19:14:39 |
| Arian | but it feels kinda annoying that the most common request is the slowest request | 19:14:50 |
| Arian | Found old meeting notes:
https://nixos.wiki/wiki/Maintainers:Fastly
| 19:15:48 |
| Arian |
Cache aggressive: ~1 month. (STATUS: NOT DONE -- requires upstream Hydra tooling changes, so cache uploads have their potential 404s purged in a timely manner.)
| 19:15:57 |
 emily | I would guess sending a purge request would not be a very invasive Hydra change. (maybe if they need to be batched?) | 19:19:56 |
 Zhaofeng Li | it could even be done on the S3 end too | 19:22:18 |
| Arian | I'm not sure howe we could do this on the S3 end | 19:35:07 |
| Arian | Ah you mean: detect when something gets pushed to S3? | 19:35:31 |
| Arian | oh yeh we could do that. We could have a Lambda or something that triggers on S3 uploads and purges the path from fastly | 19:36:13 |
| Arian | we do 12,078,871 PUTs per month
lambda costs 20cts per million requests. So this would cost $2.40
We could have a simple lambda trigger for each PUT and send a curl -XPURGE to the specific url in fastly
| 19:45:18 |
| emily | is it billed on the fastly end? | 19:53:12 |
| Arian | dont think so | 20:08:55 |
| 11 Jul 2025 |
|  @rnhmjoj:eurofusion.eu joined the room. | 09:32:39 |
| @rnhmjoj:eurofusion.eu | just to be sure, to get the name of a test for the tested job (nixos/release-combined.nix) I take the attribute name and replace nixosTests with nixos.test, right?
es. nixosTests.networking.networkd.bridge -> nixos.tests.networking.networkd.bridge | 09:38:57 |
 sterni | Seems to happen a lot in staging-next at the moment as well, haven't been able to trigger this on any of my own machines yet even with big rebuilds… | 09:48:27 |
 K900 | I wonder if this is related to @DavHau's patchShebangs changes | 09:52:51 |
 dramforever | sterni: do you have a concrete example package? i want to take a look at what could possibly be in the build process | 09:55:02 |
 @hsngrmpf:matrix.org | staging-next doesn't seem to have the latest fix for patch-shebangs | 09:55:06 |
| K900 | We're getting close to the end of the cycle now | 09:58:02 |
| @hsngrmpf:matrix.org | Opened a backport PR against staging-next: https://github.com/NixOS/nixpkgs/pull/424278/files | 09:58:03 |
| dramforever | oh that would make sense, the haskell Setup is usually binary | 09:58:42 |
| K900 | We can't | 09:58:59 |
| K900 | It'll scrap the entire cycle | 09:59:03 |
| sterni | dramforever: https://hydra.nixos.org/build/301811455/nixlog/1 | 09:59:49 |
| K900 | I'm running a new eval on -next | 10:00:10 |
| sterni | DavHau: does that try to patchShebang every binary in parallel with other phases? | 10:00:13 |
| K900 | And will restart all failed after | 10:00:16 |
