Bundled SQLite core predates the 3.51.3 WAL-reset fix (silent loss of committed writes under concurrent checkpointing)
维护者通常 11 天内回复
还没有人认领这个 Issue。
评估
调研方向
首先定位 libsql-ffi crates 中打包的 SQLite 源码和随附的 sqlite3.h,然后将打包的 checkpoint 路径与 SQLite 3.51.3 的 WAL-reset 修复进行比较。使用所描述的并发写入者、外部 WAL checkpoint、已提交键断言以及 integrity_check 轮次验证此次更新或 backport。
由索引模型根据 Issue 内容生成。
描述
Summary
The SQLite core bundled in libsql-ffi predates the upstream fix for the WAL-reset race — the ~16-year-old bug where a write transaction racing a checkpoint during WAL reset confuses the checkpointer about which pages were copied, so committed writes are silently lost or the database corrupts. Upstream SQLite fixed it in 3.51.3.
Versions checked (by reading the shipped sqlite3.h in the crates, 2026-08-12):
libsql-ffi0.9.30 → bundledSQLITE_VERSION "3.45.1"— pre-fixlibsql-ffi0.10.0-pre.4 → bundled 3.47.0 — still pre-fix
As far as I can tell there is no libsql release carrying the fix.
Why this matters to libsql users specifically
The triggering topology is a separate process checkpointing while other connections write — exactly the shape of running Litestream (or any external checkpointer) against a WAL database. That is a common libsql/sqlite deployment pattern. It is a tight-timing race, but Tailscale hit it repeatedly in production over six months, and Antithesis reproduced it deterministically in ~15 minutes.
Sources:
- SQLite fix (3.51.3): the added WAL-reset check in the checkpoint path
- Antithesis reproduction: https://antithesis.com/blog/2026/wal-reset-bug/
- Tailscale production postmortem: https://tailscale.com/blog/sqlite-wal-reset-bug
Ask
Rebase the bundled core to ≥ 3.51.3, or backport the checkpoint-path fix to the currently bundled versions. Happy to provide our reproduction/verification harness methodology if useful: N writer processes through the client, an external process issuing wal_checkpoint(TRUNCATE/RESTART) aggressively, asserting every committed key remains readable plus integrity_check per round. (For what it's worth: on 3.45.1 we did not reproduce the race in bounded runs — expected for a tight-timing bug, and not evidence of safety; the upstream fix plus that harness passing on 3.51.3 is what we ended up trusting.)
- 主要语言
- C
- 星标
- 17.3k
- 派生
- 562
- 平均合并
- 10 天 15 小时
- 30 天内合并 PR
- 1
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
tursodatabase/libsql 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
tursodatabase/libsql#2320 ·
维护者通常 11 天内回复
-
`cloudflare` feature: hrana streams are never closed可能已有人在做 @pcbeingused333 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
tursodatabase/libsql#2312 ·
维护者通常 11 天内回复
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batch可能已有人在做 @pavanmanishd 于 25 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
tursodatabase/libsql#2298 · 1 条评论 ·
维护者通常 11 天内回复
-
Rust local Row::get_value truncates embedded NUL TEXT and panics on malformed UTF-8 (0.9.30)可能已有人在做 @Sanjays2402 于 35 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
tursodatabase/libsql#2285 ·
维护者通常 11 天内回复
-
libsql-ffi: broken builds under Nix on macOS可能已有人在做 @frectonz 于 85 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
tursodatabase/libsql#2275 ·
维护者通常 11 天内回复
查看 tursodatabase/libsql 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 70/100
libretro/parallel-n64#858 ·