tursodatabase / tursodatabase/libsql
Add valgrind tests
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Adding valgrind tests to CI could enable us to check for memory leaks related to sqlite3 resources.
- Add valgrind memory leak tests for auto clean up of prepared statements
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
The issue names no files or existing tests. Start by locating the CI configuration and tests covering prepared-statement cleanup, then add a Valgrind leak check for automatic cleanup and confirm it runs successfully in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- ci-cd, databases, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100