chore(schedule): activation daemon error logging with exc_info and documentation standards #232
Labels
No labels
blocked
bug
enhancement
high-priority
low-priority
needs-info
needs-triage
ready-for-agent
ready-for-human
referenced
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gabogg/hikcentral#232
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Follow-up for PR #177 (next-day settings activation, #114) addressing pass-3 review findings P3-J and P3-Q:
Scope
activate_due_pending_changes_async, the activation catch-all logs with an f-string withoutexc_info=True. A permanently failing pending change causes error log spam on every background tick and request. Log with proper exception tracebacks (logger.exception/exc_info=True) and structured context.docs/agents/anddocs/standards/to reflect next-day activation architectural patterns, effective reset schedules (occupancy_effective_resets), and pending settings staging conventions introduced in #114 and ADR 0007.Acceptance Criteria
logger.exceptionwith change ID and payload context.docs/agents/anddocs/standards/reflect the next-day settings activation architecture, contiguous cycle transitions, and staging patterns.Refs #177, #114.