tursodatabase / tursodatabase/libsql-js
Bad error handling if caller doesn't await for sync
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
We had reports on Discord from someone that they were seeing "random errors" with embedded replicas. Turns out it was faulty application that forgot to await on sync. However, there's no excuse for us to give such terrible experience on reporting the errors so let's improve that.
Contributor guide
No contributing guide indexed for this repository
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 tracing the sync API used with embedded replicas and review the existing error-handling tests and call paths. Clarify the expected behavior when a caller omits await, then verify that this case produces a consistent, useful error without regressing normal synchronous use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100