Closed tfabris closed 2 months ago
Should be fixed with checkin 02cf0ab. Only the logging has changed, the actual handling of the videos remains the same. This is by design: I still want to see these orphaned "upcoming" videos appear in the playlist and on the web site, so that I can address and fix whatever issues caused it (for example, addressing bug #93, or perhaps just hand-deleting the orphaned video when needed). But I don't need the log to infinitely repeat the chattiness about the orphaned video being a cache miss every time.
Secondary bug caused after issue #93 occurred. When an "upcoming" video is orphaned, the CrowCamCleanup process repeatedly thinks it is a cache miss and needs to be dealt with. The log repeats these entries forever, for every run of the cleanup process:
To do: Figure out how the cleanup process can tell the difference between a true new/working video and an orphaned "upcoming" video. Perhaps it already knows (the lack of a RecordingDate seems to be the trigger) and all we need to do is suppress the logging if that's the only new cache miss for that run.
In particular, I don't want to skip the step where it continues to save the entry to the playlist and the videodata file. It is useful to me to see the orphaned video in the videodata file so that I know it's there when I look at my web page. Really, the main problem here is just how it clogs up the log entries.