I think the credit belongs to Sascha still. Look at this:<p>> The agent surfaced a suspicious issue: the anetd pods in our Google Kubernetes Engine cluster were restarting constantly, around 120 restarts per pod over six days, which is almost one crash per hour. Surely, this couldn't be right!<p>> Sascha dug into the crash dumps. The stack trace pointed to a concurrent map-access panic, multiple goroutines trying to read and write to the same data structure at the same time without proper locking. But the key detail was where the panic happened: inside the Wireguard module of anetd.<p>AI: Your anted pod is crashing.<p>Engineer: Looks in the logs and finds a stack trace.<p>Your agent didn't find the bug. It's really that simple.
This article reeks of desperation. I'm pretty sure Lovable's days are numbered.
Isn't this like the #1 problem people have with wireguard? I've had clients with the MTU issue every time I've set it up for more than a few clients. Also how on earth is "connection reset by peer" dreaded?
hate how it all has the same tone now
Oh my, a bug in Wireguard? What did Google change, since it affects only them? Any lessons learned about modifying cryptographic software?<p>...<p>Skipping past the investigation bit (minimising my daily slop intake), it's a wrong MTU value causing failing connections when Wireguard is disabled:<p>> When we disabled WireGuard, we expected the configuration to change to use the full 1500 bytes. However, some nodes in the cluster hadn't been restarted [and were] using the old 1420-byte MTU.<p>> [paraphrased] This particularly affected Valkey connections because they were distributed across nodes with mismatched MTU settings. So your API pod might not connect. The fix was rerolling all the nodes to get a consistent MTU configuration<p>Great idea, rebuild a whole fleet of VMs instead of adding the MTU configuration to your wg-down script
This piece might be a record for how quick it took me to smell the AI-tone and close the tab.. one paragraph! I'm sure it's an interesting bug but I can't stomach reading any more slop.
I think "AI-tone" is a much better way to characterize this stuff than accusing people of using AI. The problem has always been the same. Putting out slop feels disrespectful to the people you want to read/watch your stuff.<p>Makes me think of how pre-chatGPT I still could barely handle most recipe blogs because of their well known attempts at "filling space". And yea the problem is significantly magnified now everywhere else.<p>Anyway, my point is, whether or not someone uses AI is almost secondary in a way (even though it can seem pretty obvious to most of us when it's being used). All that matters is if the writing seems like it cares more about throwing words at people instead of actually conveying its points in a way to elicit understanding.
Came here to say this. It’s a shame that I’m so exhausted reading slop that I’m probably missing many interesting stories from the industry