mirror of
https://github.com/ClusterCockpit/cc-backend
synced 2026-03-24 08:37:30 +01:00
Jan Eitzinger
9fff22afce
Entire-Session: 7916ffa0-cf9e-4cb7-a75f-8a1db33c75bd Entire-Strategy: manual-commit Entire-Agent: Claude Code Ephemeral-branch: entire/7f3eb44-e3b0c4
23 lines
552 B
Markdown
23 lines
552 B
Markdown
# Session Context
|
|
|
|
## User Prompts
|
|
|
|
### Prompt 1
|
|
|
|
Implement the following plan:
|
|
|
|
# Plan: Improve scanJob logging
|
|
|
|
## Context
|
|
|
|
`scanJob` in `internal/repository/job.go` (line 162) logs a `Warn` for every scan error, including the very common `sql.ErrNoRows` case. This produces noisy, unhelpful log lines like:
|
|
|
|
```
|
|
WARN Error while scanning rows (Job): sql: no rows in result set
|
|
```
|
|
|
|
Two problems:
|
|
1. `sql.ErrNoRows` is a normal, expected condition (callers are documented to check for it). It should not produce a warning.
|
|
2. When a real scan er...
|
|
|