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.
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.
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found adopting
1.0.0-RC.2in Voyage (QRun-IO/Voyage#112) and qqq-all (QRun-IO/qqq-all#30):reconcileCronExpressionwith noreconcileCronTimeZoneIdpasses the QBit's validation but fails at startup. Validation should reject it, or a default should be applied and documented.QApplicationLauncher, or that a reconcile cron needs a Quartz scheduler. Add both to the README anddocs/MIGRATION-1.0.md.Part of #12.