tursodatabase / tursodatabase/libsql
Do integrity check in `sync` and `pull` in offline sync
Open
Nobody has claimed this yet.
offline writes
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Whenever we bootstrap the db and pull wal frames, we should do an integrity check. Integrity check is expensive, so may be we can do quick check instead.
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
Locate the offline sync paths that bootstrap the database and pull WAL frames, then trace where those operations complete. Add a quick integrity check after both operations and verify that sync and pull handle its result as expected; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100