tursodatabase / tursodatabase/libsql
Should we modify MAX_CONCURRENT_DBS && DB_CREATE_TIMEOUT via ENV or config files?
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
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 inspecting libsql-server/src/lib.rs at lines 70-71, where MAX_CONCURRENT_DBS and DB_CREATE_TIMEOUT are referenced. Determine how those values are currently set and whether the issue has a defined configuration source or expected behavior; the issue text does not specify an acceptance criterion for completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100