The scanIssues and scanIssuesWithDependencyType helper functions were not checking rows.Err() after iterating through query results. This could cause errors during iteration (connection drops, context cancellation, etc.) to be silently ignored. Per Go database/sql best practices, rows.Err() should always be checked after a rows.Next() loop completes to catch any errors that occurred during iteration. Co-authored-by: Steven Syrek <steven.syrek@deepl.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>