Release a libsql version that includes #2261 (local connection double close)

未关闭
#2,307 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 11 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
半天
新手友好度
15/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
c, go, rust, sqlite
领域
databases, release

调研方向

This is a maintainer request to publish a new libsql tag that includes the fix from #2261, which is already merged; nothing in the payload asks for a code change. The release history is the place to look, starting from the latest tag libsql-0.9.30 and the merge of #2261. Done means a tag newer than 0.9.30 exists and contains the local Connection double-close fix. Contributors can help by testing a release candidate.

由索引模型根据 Issue 内容生成。

描述

Hi! #2251 (local Connection closed twice on drop; sqlite3_close_v2 on a freed handle) was fixed by #2261 on 2026-10-13, thank you. The newest tag, libsql-0.9.30 (2026-03-19), predates the fix, so no release carries it yet.

Through go-libsql, the C binding's libsql_disconnect runs the drop on RT.spawn_blocking. In our CI that shows up as a random SIGSEGV on a tokio worker (sqlite3_close_v2 ← drop_in_place<libsql::local::connection::Connection> ← Arc::drop_slow ← tokio::runtime::task::raw::poll) in about 4–12% of test-binary runs on ubuntu-latest. Production services that close connections (pool retirement, shutdown) carry the same double free.

Could you cut a release (0.9.31 or later) that includes #2261? That would let go-libsql rebuild its static libraries (update-libsql.yml) and let us drop a fork that only cherry-picks this one fix. Happy to test a release candidate.

主要语言
C
星标
17.3k
派生
562
平均合并
10 天 15 小时
30 天内合并 PR
1

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tursodatabase/libsql 的其他 Issue

查看 tursodatabase/libsql 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。