now http/2 works again. And the point was not that cf might have had a problem, the point is that we should not deliberately destroy simple, working protocols

Dass ich damit auch die Unterstuetzung fuer Journalist:innen und andere Mitarbeitende entziehe, bedauere ich. Ich wuerde mir sehr eine Neugruendung eines guten IT Verlags mit klarem Ethikkodex wuenschen.

@jbcrawford i have zfs'd

"ESC gehört der AWS European Sovereign Cloud GmbH, ... das eine hundert­pro­zen­tige Tochtergesellschaft seiner amerikanischen Muttergesellschaft ist. ... Anschein einer europäischen Eigentümerschaft, ... Die AWS ESC hat daher nur eine eingeschränkte operative ... und ... keine technologische […]

@gabrielesvelto yes, i know the memory error thread, thank you. ECC absolutely is a must and in this regard i am glad that my code (usually) does not run on consumer devices. fwiw, relying on every single bit in a multi-tb ram system still feels scary at times, and it is amazing that these […]

@slink this crate can detect patterns that suggest a memory error was encountered or that the crash was inconsistent and thus most likely due to a hardware bug. If you check out the output schema of the tool you'll find two fields called "possible_bit_flips" and "crash_inconsistencies" that […]

@slink oh yes, we have tools for that. First however I'd point you to my thread about memory errors because those are even more common when analyzing crashes: https://fosstodon.org/@gabrielesvelto/112407741329145666

For crash analysis we have a rust crate to analyze minidumps, which we generate […]

@gabrielesvelto thank you for this great, informative overview.
numerous times, i had asked myself if a reported crash could be caused by a hardware bug, and so far i would think i never saw a real case - possibly due to the software i work on running in more controlled environments.
but i would […]