tursodatabase / tursodatabase/libsql

Sqld Server will not work with offline-writes

Open
#2,037 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
17.2k
Forks
531
Avg merge
1h 12m
Merged PRs (30d)
1

Description

When using offline: true in my client connection in conjunction with my local slqd docker image (ghcr.io/tursodatabase/libsql-server:latest) i get this error.

Unhandled Exception: PanicException(called Result::unwrap() on an Err value: Sync(PullDb(404, ""))Backtrace [{ fn: "_ZL15__pthread_startPv" }, { fn: "__start_thread" }])

sqld info:

version: 0.24.32
commit SHA: 1e0ce80aa2bb1d20fc3e526409bf46b4eadd720d
build date: 2025-04-17

when i search in libsql github for PullDb() i get here:
https://github.com/tursodatabase/libsql/blob/1e0ce80aa2bb1d20fc3e526409bf46b4eadd720d/libsql/src/sync.rs#L479C30-L479C35

it wants to check an /info API endpoint but this is not available in sqld server.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with libsql/src/sync.rs around line 479 and reproduce the failure using offline: true with the ghcr.io/tursodatabase/libsql-server:latest image. Investigate the PullDb path and the missing /info endpoint in sqld server; done means offline writes no longer panic when used with this server.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, rust
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.