"SqliteFailure" with a remote replica
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust, sqlite
- Domain
- databases, distributed-systems
Research direction
Start by reproducing the insert failure with libsql 0.9.3 in remote replica mode, then compare it with local replica, local-only, and remote modes while enabling RUST_BACKTRACE=1. Inspect the reported db.rs locations around lines 539 and 343 and determine the conditions that produce the malformed schema error. Done means the failure has a confirmed cause and a verified fix or clear reproduction boundary.
Written by the indexing model from the issue text.
Description
Hi! I've been using libsql for my project, and lately I've been having this problem:
thread 'actix-server worker 2' panicked at /var/home/sergio/Documentos/staticcms/rusty/src/db.rs:539:40:
: SqliteFailure(11, "malformed database schema (?)")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
I've tried other modes to see if I could harvest more info:
In local replica mode:
thread 'actix-server worker 2' panicked at /var/home/sergio/Documentos/staticcms/rusty/src/db.rs:343:22:
Compilation of SQL sentence failed: Misuse("Cannot describe in local replica mode.")
(Honestly, this might be something I'm doing wrong, but could be of interest).
In local only:
It works fine, but I get:
2025-06-26T20:28:26.488910Z ERROR libsql::local::connection: Failed to clear authorizer during disconnect
In remote:
It also works fine.
Some details:
- I'm using 0.9.3, I can't use anything newer due to the bug that requires a multithreaded runtime, however I can't use it.
- Reading works fine, and even removing, seems like this error is cause by an insert (haven't tried modifications).
- 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 ·