| 10 Jun 2025 |
 flokli | In reply to @arianvp:matrix.org
I guess even for 200 OK narinfos we could set Cache-Control: immutable. Just not for 404s That makes it very hard to update the contents, if we want to roll out new keys, or update nar paths to point elsewhere | 11:34:49 |
 emily | (probably low value for narinfos anyway considering how small they are and it not helping 404 latency?) | 11:42:30 |
 Arian | In reply to @flokli:matrix.org
That makes it very hard to update the contents, if we want to roll out new keys, or update nar paths to point elsewhere okay so not for narinfos. But for NARs this seems totally safe right? | 11:47:46 |
| emily | theoretically, a drv hash does not uniquely identify the built results. however I heard that rebuilding something in the cache without changing drv hash is not something that can feasibly be done right now, so I assume the risk is very low | 11:48:30 |
| emily | maybe there could be an issue if a NAR has legal problems and we need to take it down? but I have to assume Fastly has knobs to purge stuff manually if we have to | 11:48:53 |
| Arian | Fastly can purge yes | 11:49:04 |
| Arian | https://github.com/NixOS/infra/pull/727/files hypothetical proposal | 12:30:41 |
| emily | heads up – https://github.com/NixOS/nixpkgs/pull/415566 we're expecting on the Darwin team end that we'll want to turn off x86_64-darwin on the jobsets sometime between after 26.05 branch-off and the release of 28.11, most likely after either 26.05 or 27.05 branch-off | 13:06:07 |
| emily | (if it's around branch-off, then for the unstable branch only of course, until the end of the support period for the branched-off release) | 13:06:38 |
 Vladimír Čunát | That will help staging* iterations quite a bit, I expect. | 13:12:27 |
| emily | indeed | 13:12:47 |
