| 4 Oct 2021 |
 K900 | I don't really know much about how Netlify works, but right now status.nixos.org and monitoring.nixos.org both resolve to the same IPv4 | 13:19:47 |
 Jonas Chevalier | planet.nixos.org has a A, CNAME and NETLIFY record | 13:19:48 |
| K900 | And both redirect to https://status.nixos.org/ | 13:19:54 |
| K900 | Which loops forever | 13:19:56 |
| K900 | This is using Cloudflare's name servers so shouldn't be ISP fuckery | 13:20:43 |
|  Janne Heß left the room. | 13:27:10 |
| Jonas Chevalier | tracking here: https://github.com/NixOS/nixos-org-configurations/issues/177 | 13:35:18 |
| Jonas Chevalier | both the old A record and the new NETLIFY records were living side-by-side. This should be fixed now once DNS propagates (~1h) | 13:40:51 |
| K900 | Thanks, seems good now :) | 13:54:13 |
|  Baughn joined the room. | 19:52:20 |
| Baughn | The iso files for the gnome desktop, as well as both minimal installation images on nixos.org don't match their sha256sums. | 19:52:51 |
 Vladimír Čunát | The sums are for a different commit than the actual ISOs. | 19:56:56 |
| Vladimír Čunát | For minimal I see:
21.05.3509.7daf35532d2
21.05.3468.92609f3d9bc | 19:57:39 |
| Baughn | Mmyep. There's the bug. | 19:58:34 |
| Vladimír Čunát | I wonder if it's possible that these redirect pairs aren't guaranteed to be "cached atomically" by Fastly or something. | 19:59:41 |
|  Linux Hackerman joined the room. | 19:59:42 |
|  djacu joined the room. | 19:59:51 |
| Vladimír Čunát | * I wonder if it's possible that these redirect pairs aren't guaranteed to be "cached atomically" by Fastly or something. (well, I don't know this stuff) | 20:00:08 |
| Baughn | I'd call that virtually guaranteed | 20:00:12 |
| Baughn | As in, guaranteed not to work | 20:00:22 |
| Baughn | We'll find out in a couple minutes. | 20:00:27 |
| Baughn | An ideal fix would be to have a JSON file on the website which points to the iso, and also contains the sha256 of that iso. That's cover the browser case, at least; for the console case, you could have a single directory that's a redirect to a latest-iso dir containing both files | 20:01:41 |
| Baughn | * An ideal fix would be to have a JSON file on the website which points to the iso, and also contains the sha256 of that iso. That'd cover the browser case, at least; for the console case, you could have a single directory that's a redirect to a latest-iso dir containing both files | 20:01:48 |
| Linux Hackerman | That's one option. Surely the CDN should have a way to invalidate caches though? | 20:02:11 |
| Baughn | Probably, but don't go that path. Cache invalidation is the hardest problem in computer science. | 20:02:56 |
| Baughn | Much, much better to use a construction that makes it unnecessary. | 20:03:05 |
| Linux Hackerman | True | 20:04:39 |
| Baughn | I'd be happy to supply the PRs to fix this, honestly... dunno where I should look, though! | 20:05:32 |
|  Sushi Dude joined the room. | 20:07:18 |
| Baughn | Found it~ | 20:18:25 |
