[BUG] No Database Connection Pooling

[olddev94]

Project

vgrep

Description

The server creates a new SQLite database connection for every request to /status and /search endpoints. This is inefficient and can cause issues with connection limits and SQLITE_BUSY errors under load.

Error Message

Potential `SQLITE_BUSY` under concurrent requests.

Debug Logs

System Information

- Bounty Version: 0.1.0
- OS: Ubuntu 24.04 LTS
- Rust: 1.75+

Screenshots

No response

Steps to Reproduce

1. Start server: vgrep serve
2. Send many concurrent search requests
3. Each request opens a new database connection
4. Potential for resource exhaustion or busy errors

Expected Behavior

1. Single database connection (or pool) in ServerState
2. Connection reused across requests
3. Proper connection pooling for concurrent access

Actual Behavior

1. New Database created per request
2. Connection opened and closed for every request
3. File descriptor churn
4. Potential SQLITE_BUSY under load

Additional Context

No response

[echobt]

Issue validated. The reported problem has been confirmed in the codebase. A Pull Request with the fix has been submitted: CortexLM/vgrep#50.