MythFillDB should use the run time the provider suggested

[Frank Phillips <fphillips81@…>]

In mythtv-setup, the help text of MythFillGrabberSuggestsTime says this option is mutually exclusive with the FillDB hour window settings. This intention was probably lost with the housekeeper rewrite in May.

programs/mythbackend/backendhousekeeper.cpp: MythFillDatabaseTask::DoCheckRun

Currently, when MythFillGrabberSuggestsTime is enabled, the MythFillDB task will only be run when inWindow and also near MythFillSuggestedRunTime. A wide window (0-23) is a workaround. For the most part the suggested time feature is nullified, I guess leaving it up to DailyHouseKeeperTask to run MythFillDB.

[Frank Phillips <fphillips81@…>]

Backend started as scheduled to run MythFillDB, but did nothing, then shutdown.

[Frank Phillips <fphillips81@…>]

Backend correctly wakes and runs MythFillDB.

[Frank Phillips <fphillips81@…>]

Applies to master and fixes/0.27 ​https://github.com/fphillips/mythtv/commit/8fe0bff515808ffafe017da01043354dd5eb8e55

[Frank Phillips <fphillips81@…>]

I know my writing is terse, sorry about that. I had hell with college papers. I'll elaborate:

The housekeeper misses potential suggested run times when you have a narrow window set (I have 2-5). The suggested time would have to fall into the window to be run, otherwise it is skipped because both conditions need to be true.

In my failed-to-run attachment, it woke for a suggested run time of 12:11, but failed the inWindow conditional and did not queue the task.

As alluded to above, someone with an infinite window set (0-23) would not experience this and the runs would happen at suggested times.

[sphery]

Previously the housekeeper ignored the run window when you enabled the setting:

Run guide data program at time suggested by the grabber. If enabled, allow a DataDirect guide data provider to specify the next download time in order to distribute load on their servers. Guide data program execution start/end times are also ignored.

(as described in the help text). Some on IRC claimed (in Oct '13) this is a bad idea (though it had been like that for 6 1/2 years before the discussion (which was triggered by the change in the new housekeeper).

So, either we ignore the run window (as before), or alternatively, we allow (and schedule for wakeup, when appropriate) mythfilldatabase runs during the next window after the grabber-suggested run time. Note, however, that running in the window after the suggested run time may result in skipping a day, which would mean users whose grabbers don't pull all data (including all Schedules Direct users who do not add the --dd-grab-all argument to their "Guide data arguments" setting) may not get some "tomorrow" updates from a standard tomorrow/+13 run (i.e. they get tomorrow on Monday, not Tuesday, then on Wednesday, so they lack updates for listings on Tuesday's tomorrow).

See #3302 and [ce20f46b] .

[Frank Phillips <fphillips81@…>]

More info at ​http://forums.schedulesdirect.org/viewtopic.php?f=5&t=2541#p7623

[Frank Phillips <frankalso@…>]

In ff22b7199e6bf77105d2206a7945c2dd5b06b697/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[Frank Phillips <frankalso@…>]

In 5c34db0fa3da9bccf4cf16c696b34d12d08c5fa6/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available