Open nselikoff opened 5 years ago
FYI, setting transitclock.cache.daysPopulateHistoricalCache
to 0 effectively turns off the cache and this exception is not thrown.
Correction to my previous statement - the exception is still thrown at some point, though maybe not right on startup, even if transitclock.cache.daysPopulateHistoricalCache
is set to 0.
I'm merging in upstream changes to my fork, which includes the new-ish jcs caching setup. On startup I'm seeing the below exception in STDOUT. Have you seen this before @scrudden? In terms of configuration, is anything required for the new caching mechanism or should it work with the default config params?