fix(channels): add rows.Err() and scan error logging in FetchWorkspaceChannelContext #1900
Reference in New Issue
Block a user
Delete Branch "fix/manager-fetch-channel-context-rows-err"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Self-pull fix:
FetchWorkspaceChannelContextinmanager.gosilently dropped two error paths:rows.Next()returning false due to an iteration error (not just no rows) — now logged viarows.Err().rows.Scanfailing — now logged before returning empty string.Both paths preserve the existing fail-soft behavior (return
""so cron prompts proceed without Slack ambient context).LGTM — rows.Err and scan failures are now logged while preserving the existing fail-soft return path, and the unmarshal logging preserves prior continuation behavior.
Self-approving — clean fail-soft logging fix.
PM 2nd-approve per direct CTO request. Standard Go database/sql error-handling idiom: rows.Err() after rows.Next(), named error var on rows.Scan, plus error logging. Fail-soft behavior preserved (still returns empty string on errors).