IDLE wakeup now logs every processed UID — document and consider gating #30

Open
opened 2026-05-12 09:34:45 +02:00 by heiko · 1 comment
Owner

Found during review of #24.

With ReportProcessed: true in the IDLE path, every UID processed after an IDLE wakeup is now logged (not just matches). On a busy mailbox this can substantially increase log volume.

Two small follow-ups:

  1. Document this under the scan=idle description in doc/admin.md so operators expecting "only matches logged" aren't surprised.
  2. Consider whether ReportProcessed should be gated by --verbose or a dedicated flag, instead of being unconditional on the IDLE path. The startup/initial paths deliberately stay quiet for unmatched messages; IDLE diverges from that convention.

Refs: PR #24

Found during review of #24. With `ReportProcessed: true` in the IDLE path, every UID processed after an IDLE wakeup is now logged (not just matches). On a busy mailbox this can substantially increase log volume. Two small follow-ups: 1. Document this under the `scan=idle` description in `doc/admin.md` so operators expecting "only matches logged" aren't surprised. 2. Consider whether `ReportProcessed` should be gated by `--verbose` or a dedicated flag, instead of being unconditional on the IDLE path. The startup/initial paths deliberately stay quiet for unmatched messages; IDLE diverges from that convention. Refs: PR #24
Author
Owner

Related commit: 2305c33. The idle wakeup path still reports every processed UID with scan=idle, so this behavior is still present.

Related commit: 2305c33. The idle wakeup path still reports every processed UID with scan=idle, so this behavior is still present.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
IUS/xr-invoiced#30
No description provided.