ores.scheduler.api.tests fails on main since the vcpkg updat…
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
ores.scheduler.api.tests fails on main since the vcpkg submodule update of
2026-10-05 (978e1e098d). The case "cron_expression::from_string rejects
invalid expressions" expects the six-field * * * * * * to be refused, and
from_string accepts it.
from_string prepends a seconds field before it calls croncpp, so a
six-field input reaches the library as seven fields. The newer croncpp
evidently accepts seven; that the extra field is read as a year is a guess, not
checked against its source.
2. Why
A cron expression is five fields in this system. Without a field count of its own, which inputs pass depends on the vendored library's version. The fix is to require exactly five fields before the prepend, which keeps the test as it is.
3. References
projects/ores.scheduler/api/src/domain/cron_expression.cpp,from_string.projects/ores.scheduler/api/tests/domain_cron_expression_tests.cpp, line 61.- Found by the full test run of Honour as_of on every generated list read, which changes nothing in scheduler.