Release a libsql version that includes #2261 (local connection double close)
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Half a day
- Newbie friendliness
- 15/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C
- Stars
- 17.3k
- Forks
- 562
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tursodatabase/libsql
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tursodatabase/libsql#2320 ·
Maintainers usually reply within 11 days
-
`cloudflare` feature: hrana streams are never closedPossibly taken @pcbeingused333 claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/libsql#2312 ·
Maintainers usually reply within 11 days
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batchPossibly taken @pavanmanishd claimed this 25 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tursodatabase/libsql#2298 · 1 comment ·
Maintainers usually reply within 11 days
-
Rust local Row::get_value truncates embedded NUL TEXT and panics on malformed UTF-8 (0.9.30)Possibly taken @Sanjays2402 claimed this 35 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tursodatabase/libsql#2285 ·
Maintainers usually reply within 11 days
-
libsql-ffi: broken builds under Nix on macOSPossibly taken @frectonz claimed this 85 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
tursodatabase/libsql#2275 ·
Maintainers usually reply within 11 days
All issues in tursodatabase/libsql
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·