tursodatabase / tursodatabase/libsql
The behavior for concurrent control for DB in libsql
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
In my code, I tried to use the libsql server via direct HTTP call. Some error message has been raised like "Timed out while openning database connection".
I find the code here https://github.com/tursodatabase/libsql/blob/main/libsql-server/src/connection/mod.rs#L253-L295
And I find seems there is no place to release the Semaphore except to close the current connection?
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 at libsql-server/src/connection/mod.rs:253-295, then trace the direct HTTP connection path and the Semaphore's lifecycle. Determine whether the permit is released only when the current connection closes; done means the timeout and concurrent-connection behavior, including the expected release point, are made explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100