Yes, although that's not new. The amount of different exploits and RCE I've seen in the past decade from just "opening" an PDF is mind blowing. Not sure if it's slowed down but around 8 years ago ghostcript would patch a couple of RCE from PDF processing every few months.
It's worth noting that GPUs have a much higher failure rate than traditional CPUs. Over 10x the failure rate due thermal stress. The amount of heat generated is very different. You can't really replace a GPU in a satellite (at least today?) which would place most of these satellites as space debris in a ~5 year horizon.
It's been a while since I've checked this but a few years ago we tried to limit test kine on a large-ish cluster and it performed pretty poorly. It's fine for small clusters but the way they have to implement the watch semantics makes it perform poorly (at least this was the case a few years ago).
The node failure rate is much higher than that. On a 1M node cluster of cloud-managed instances (AWS, GCP, Azure, etc.) you'd likely see failures a few times a month, if not more.
It depends on how much effort you put into it vs. just using any of the base templates/components that Tailwind Plus (previously Tailwind UI) has to offer.
If you look at their Showcase section[1], you can't tell it's using TailwindCSS for most of them (imo).
Jeremy Rubin built a proof-of-concept for this over a decade ago for a hackathon and ended up being sued by the state of New Jersey. This blog post[0] has a good summary of the events.
It depend on the UUID version you're using. Version 4 (Random) will always have that value be 4 as per RFC 9562. So 99999999-9999-9999-9999-999999999999 is a valid UUID but not a valid UUID v4. If you wanted to be pedantic the website should have been named https://everyuuidv4.com/
There's some explicit differences with Python[1]. My understanding is that Starlark was specifically created for Bazel so if I had to guess it's to enforce the immutability of values between contexts.
Thank you for TA'ing the class! I took it in 2015 and TAs really made the class for myself and most of my friends.
Is the end of semester Leisserchess competition still going? I believe I heard that the year you TA'd it (might have been a year before or after) a group finally compiled an opening playbook and beat everyone in the class
It might be plan dependent(?) but everything you’re describing is configurable on your PagerDuty profile. I have it configured to send me a notification immediately followed by a call if I don’t acknowledge it within a minute (yes, this is aggressive but I’m in a high urgency, quick response time SLA rotation)
> Shocked that no VC or group of them haven't stood up a short term bridge loan facility since it was them who triggered the chain reaction that took the bank down.
(Disclaimer: I haven't looked too much into this tool other than a cursory glance)
It seems this tool isn't meant mostly for testing how different components behave under different scenarios and/or load. This is probably particularly helpful for custom controllers or operators. What happens to your controller if it's constantly reconciling 100k pods? What about 5k nodes? Something else? If this tool makes creating a "loaded" cluster easy, it's definitely handy. Would have saved me some time doing something similar a few months ago.
For what it’s worth sometimes it’s worth abandoning old legacy context in a rewrite if the new solution drastically reduces operational complexity. For example, it’s cheaper/better to retrain everyone on the new solution than it is to continue to onboard new folks to the legacy one. This is not always the case, but sometime it is as the parent comment mentions.
https://www.youtube.com/watch?v=4FdGIRBUds4