Validate the reconcile cron timezone; warn when basepull is off; document scheduler needs #29

Closed
opened 2026-10-10 00:12:15 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-10 00:12:15 +00:00 (Migrated from github.com)

Found adopting 1.0.0-RC.2 in Voyage (QRun-IO/Voyage#112) and qqq-all (QRun-IO/qqq-all#30):

  1. A reconcileCronExpression with no reconcileCronTimeZoneId passes the QBit's validation but fails at startup. Validation should reject it, or a default should be applied and documented.
  2. A config-driven table with no timestamp field silently turns off incremental basepull. Annotated tables log a warning; config-driven tables should log the same warning.
  3. The docs never say that schedules (basepull, reconcile cron) only run when the host starts through QApplicationLauncher, or that a reconcile cron needs a Quartz scheduler. Add both to the README and docs/MIGRATION-1.0.md.

Part of #12.

Found adopting `1.0.0-RC.2` in Voyage (QRun-IO/Voyage#112) and qqq-all (QRun-IO/qqq-all#30): 1. A `reconcileCronExpression` with no `reconcileCronTimeZoneId` passes the QBit's validation but fails at startup. Validation should reject it, or a default should be applied and documented. 2. A config-driven table with no timestamp field silently turns off incremental basepull. Annotated tables log a warning; config-driven tables should log the same warning. 3. The docs never say that schedules (basepull, reconcile cron) only run when the host starts through `QApplicationLauncher`, or that a reconcile cron needs a Quartz scheduler. Add both to the README and `docs/MIGRATION-1.0.md`. Part of #12.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-quick-search#29