Comment on Cloudfare outage post mortem

panda_abyss@lemmy.ca ⁨4⁩ ⁨months⁩ ago

• Thallium_X@feddit.org ⁨4⁩ ⁨months⁩ ago

  As a next step they should have wrapped everything in a true(while) loop so it automatically restarts and the program never dies

  source

  • panda_abyss@lemmy.ca ⁨4⁩ ⁨months⁩ ago

    Exactly, while True: try: main(); except: pass;

    source
• SinTan1729@programming.dev ⁨4⁩ ⁨months⁩ ago

  I hope you’re joking. If anything, Rust makes error handling easier by returning them as values using the Result monad. As someone else pointed out, they literally used unwrap in their code, which basically means “panic if this ever returns error”. You don’t do this unless it’s impossible to handle the error inside the program, or if panicking is the behavior you want due to e.g. security reasons.

  Even as an absolute amateur, whenever I post any Rust to the public, the first thing I do is to get rid of unwrap as much as possible, unless I intentionally want the application to crash. Even then, I use expect instead of unwrap to have better error logging. This is definitely the work of some underpaid intern.

  source

  • panda_abyss@lemmy.ca ⁨4⁩ ⁨months⁩ ago

    I was joking, but oof it did not go over well.

    source

    • SinTan1729@programming.dev ⁨4⁩ ⁨months⁩ ago

      Ah that makes sense. To be fair tho, there’s a lot of unwarranted hate towards Rust so it can be hard to tell.

      source

      • panda_abyss@lemmy.ca ⁨4⁩ ⁨months⁩ ago

        I should bite the bullet and learn it.

        I decided to learn zig recently, it feels like crafting artisanal software, which is what I liked C for. But it’s kinda janky in that each point version major features come and go (see io and async).

        There’s a place for engineering software which is what rust seems great at. Definitely seems like a tool I could/would use as rust is taking over many of my tool workflows.

        source
• jimmy90@lemmy.world ⁨4⁩ ⁨months⁩ ago

  honestly this was a coding cock-up. there’s a code snippet in the article that unwraps on a Result which you don’t do unless you’re fine with that part of the code crashing

  i think they are turning linters back to max and rooting through all their rust code as we speak

  source
• dan@upvote.au ⁨4⁩ ⁨months⁩ ago

  The actual issue is that they should be canarying changes. Push them to a small percentage of servers, and ensure nothing bad happens before pushing them more broadly. At my workplace, configs are tested on one server, then an entire rack, then an entire cluster, before fully rolling out. The rollout process watches the core logs for things like elevated HTTP 5xx errors.

  source
• Zwuzelmaus@feddit.org ⁨4⁩ ⁨months⁩ ago

  So you think there is no error handling possible in Rust?

  Wait until you find out that Pyhon doesn’t write the error handling by itself either…

  source