Yannick L.

Somewhere, something incredible is waiting to be known -- Carl Sagan

[Joran Dirk Greef @jorandirkgreef]

Yes, that was the fix that most DBMSes applied for fsyncgate

But most still don’t use Direct I/O when they replay the WAL on reboot.

So they risk externalizing non-durable data as durable (because they still read from the incoherent kernel page cache).

cf. “Can Applications Recover from fsync Failure?” which looked into this in 2020, two years after these fixes, and found that PG, SQLite et al were still vulnerable.

[Yannick L. @sizon5]

@aarondotdev @ptaranat There is also https://t.co/9pKKvP0i54 which I discovered in this great talk: https://t.co/6z6CuDJMHd

[Yannick L. @sizon5]

@gchampeau This is the way :-) https://t.co/MSu5Bs7UVu

[Yannick L. @sizon5]

@unclebobmartin Looks like temper: https://t.co/eH4nEnv06m

[Yannick L. @sizon5]

@ThePrimeagen @GergelyOrosz Deterministic simulation testing maybe ? Here is an example with super mario bros :-) https://t.co/Wi9IZ8CjVk

[Brink @bitcoinbrink]

Niklas (@dergoegge) outlines an approach and a solution, bedrock, for this problem of determinism.

He focuses on the challenge of emulating time and pausing a VM at an exact instruction count, something CPUs aren't designed to do.

https://t.co/w9vjZhx6QZ

[Yannick L. @sizon5]

@DominikTornow Now I have a clear picture, this is the smoking gun

[Yannick L. @sizon5]

@antirez You might be interested by this: https://t.co/MSu5Bs7UVu

[Yannick L. @sizon5]

@criccomini You might want to take a look at the publication section here, lots of great work in these areas: https://t.co/vfhGGuiXGL

[Yannick L. @sizon5]

@ibuildthecloud Absolutely. My LinkedIn post today : "Looking for a differentiator? Invest in quality" https://t.co/HTbP0sJ39J

[Quint @quint_lang]

Three ways to drive testing from a Quint spec, depending on how much control your runtime gives you:

→ Model-Based Testing: replay traces from the model
→ Hybrid: model proposes the next action based on results from runtime
→ Trace Validation: capture from production, check it against the model

A peek at @bugarela's BugBash by @AntithesisHQ 2026 talk. Full video soon!

[Kiran @kirancodes]

New 0-day in Lean just dropped. Your secure software just got borked. All your bases are mine.

https://t.co/XFrTcla2wS

[Peer Richelsen @peer_rich]

i like to think of settings like a pressure valve

every time you add one its because you avoided making a real product decision

if youre not careful your product becomes a graveyard of avoided decisions

lets just add a setting often means we dont want to pick a default

it might feel diplomatic in the moment

everyone gets what they want in the end 

except for the user

they end up with a minefield of toggles they dont understand

good products make strong choices

they say: this is how it works by default because we believe this is the best way

settings should exist for real variability

not to protect us from disagreements

when you look at an app with 200 settings youre not seeing power

youre seeing a decade of unresolved arguments

and its costing clarity for you and your customers

im not anti settings

im anti cowardice

if the only reason a toggle exists is: we didnt want to take a stance

it probably shouldnt exist

[Rohan Paul @rohanpaul_ai]

Old KPIs protect old products.

A lot of strategy is just refusing to pay the migration cost.

[Yannick L. @sizon5]

"Specy addresses this challenge by automatically
learning specifications from observable event traces generated by message exchanges in distributed systems." 🤯. I'm a huge fan of P. I can't wait to play with this.

[¬¬Mike (Deyuan) He @1SHL10]

TL;DR: we identified a pattern of FOL formula over message events (exchanged between servers) that can express various safety properties of distributed systems, and we combine static&dynamic learning to effectively discover them.
Check out our pre-print: https://t.co/hxqQQ00tFG

[¬¬Mike (Deyuan) He @1SHL10]

Happy to announce that our paper “Specy: Learning Specifications for Distributed Systems from Event Traces” has been accepted at OOPSLA’26. This is a joint effort with Ankush (@ankushpd) and the P team! It’s not possible without all the great collaborators!

[ScyllaDB @ScyllaDB]

"Scale isn't just performance or distribution, it's survivability." - @TigerBeetledev's @jorandirkgreef. At Monster Scale Summit, find out what keeps most transaction processing systems from scaling and how to survive billions of transactions. https://t.co/Bd1UcNHk4I

#ScyllaDB

[Yannick L. @sizon5]

@DominikTornow Maybe in the jepsen toolbox ? https://t.co/x5QL85Kpdq

[Yannick L. @sizon5]

@el_yawd @Keleesssss @DominikTornow I think think it is in p repo, I still did not have time to try it yet: https://t.co/sWaufiN3Bg

[Yannick L. @sizon5]

It's so easy to decide on a name https://t.co/wpEk8m8E5N