Scheduler and synthetic entities have no point-in-time list …
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
The entities of ores.scheduler and ores.synthetic have no point-in-time
list read yet. PR 2683 made as_of the default for every entity with a
validity window and applied it to the generated files by a three-way merge.
Every merge in those two components conflicted, because their generated files
predate the ordering and filter templates, so both were left out.
2. Why
Their clean-up stories, clean-scheduler and clean-synthetic, regenerate the
files, and the default then brings as_of with it. Nothing needs writing by
hand; each clean-up should check that its list protocols carry as_of and its
services refuse a malformed one with as_of_invalid.
3. References
- Honour as_of on every generated list read – the change and why the two were left out.