A schedule was being put in the memory cache AFTER trimming future intervals. This was a problem for intraday schedules, because the near-future quickly becomes present & past. So after running for a long time, YFC was claiming Yahoo data didn't map to schedule.
Fixes #51
Also improved logging slightly: set logging level via yfcl.EnableLogging()
A schedule was being put in the memory cache AFTER trimming future intervals. This was a problem for intraday schedules, because the near-future quickly becomes present & past. So after running for a long time, YFC was claiming Yahoo data didn't map to schedule.
Fixes #51
Also improved logging slightly: set logging level via
yfcl.EnableLogging()