3 ms·
Nice analysis. Boy I can’t imagine having to work at Cloudflare on this stuff. A month to get your “small in code” change out only to find some bums somewhere h
by renewiltord 9mo ago
Nice analysis. Boy I can’t imagine having to work at Cloudflare on this stuff. A month to get your “small in code” change out only to find some bums somewhere have written code that will make it not work.
- stackskipton 9mo agoOr when working on massive infrastructure like this, you write plenty of tests that would have saved you a month worth of work. They write reordering, push it and glibc tester fires, fails and you quickly discover "Crap, tests are failing and dependency (glibc) doesn't work way I thought it would."
- renewiltord 9mo agoI suspect that if you could save them this time, they'd gladly pay you for it. It'll be a bit of a sell, but they seem like a fairly sensible org.
- jeroenhd 9mo agoWith glibc falling over but systemd-resolved working as intended, I suspect their Linux tests may have accidentally passed. Most desktop Linux installs and a whole lot of cloud Linux installs would've accidentally been saved from glibc's bug by systemd-resolved.
- rjh29 9mo agoIt was glibc's resolver that failed - not exactly obscure. It wasn't properly tested or rolled out, plain and simple.
- urbandw311er 9mo agoOr — hot take — to find out that you made some silly misinterpretation of the RFC that you then felt the need to retrospectively justify.