> The bug is a data race with tight timing constraints. It is unlikely to occur in common use. The developers have never been able to reproduce the bug organically and had to add special testing logic to SQLite that deliberately triggers the circumstances of the the bug in order to verify that the issue has been fixed.
I read that and it feels like some theoretical thing versus causing impactful outages for workloads shaped like tailscale’s.
How is "Fix the WAL-reset database corruption bug" downplaying this? https://www.sqlite.org/changes.html
> The bug is a data race with tight timing constraints. It is unlikely to occur in common use. The developers have never been able to reproduce the bug organically and had to add special testing logic to SQLite that deliberately triggers the circumstances of the the bug in order to verify that the issue has been fixed.
I read that and it feels like some theoretical thing versus causing impactful outages for workloads shaped like tailscale’s.