tursodatabase / tursodatabase/libsql
Connector not being passed correctly in offline writes
Open
Nobody has claimed this yet.
bug
offline writes
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
This has been shown to be a issue on the libsql-android SDK, since we use a webpki connector.
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
Start by reproducing an offline write through the libsql-android SDK using the webpki connector. Trace where the connector is passed during offline writes and confirm that the expected connector reaches that path; done means offline writes use the webpki connector correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100