V0.2.2 testing

[CodeMeAPixel]

No description provided.

[github-actions]

📊 Code Coverage Report

Total Coverage: 1.8%

View Full Report

[sentry]

Bug: The GetDashboardStats handler ignores errors from QueryRow().Scan() calls, causing it to return a 200 OK response with misleading zero-value statistics if a database query fails.
_{Severity: MEDIUM}

Suggested Fix

Check the error returned by each h.db.Pool.QueryRow(...).Scan(...) call in the GetDashboardStats handler. If the error is not nil, return an HTTP 500 Internal Server Error response, similar to the pattern used in the GetUserAccount handler.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: internal/handlers/dashboard.go#L47-L54

Potential issue: In the `GetDashboardStats` handler, multiple database calls using
`QueryRow().Scan()` do not have error handling. If a query fails, for instance due to a
temporary database connection issue, the error is silently ignored. As a result, the
associated variables retain their default zero values. The handler then returns an HTTP
200 OK response with misleading statistics (e.g., zero servers, zero balance), rather
than returning an appropriate server error. This behavior is inconsistent with other
handlers like `GetUserAccount` which correctly handle database errors.

_{Did we get this right? 👍 / 👎 to inform future reviews.}