tursodatabase / tursodatabase/libsql
Offline database sync lag
Open
Nobody has claimed this yet.
Embedded Replicas
enhancement
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Clients need to know how much behind they potentially are. On the other hand, we might want to just expose the "last sync" timestamp for offline clients, but also, perhaps we should extend the protocol to tell exactly how many frames a client is behind without actually syncing anything.
Contributor 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.
Research direction
No files, tests, or entry points are named. Start by locating the offline sync protocol and determine whether completion means exposing a last-sync timestamp, reporting how many frames a client is behind, or both; add tests for the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100