Opened 12 years ago

Closed 11 years ago

#5337 closed defect (fixed)

Deleted programs expired early and set to rerecord when "number of episodes" is set

Reported by: msherman@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: 0.21-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I think I've found a bug in the interaction between a recording rule with max number of episodes and the deleted group.

I've got a rule (Dora the Explorer) set up with max number of episodes set to 3. I have the Deleted group set up to keep deleted programs for up to 7 days. When the scheduler decides to record a new episode of Dora, it immediately auto-expires an episode from the Deleted group, even though it hasn't been around for 7 days yet, and there are less than 3 non-deleted episodes. The expired episode gets marked for re-recording (duplicate=0) even though is was already deleted.

I think the main bug is that the max number of episodes code needs to be modified to not count episodes in the deleted group. Alternatively, it should not reset the duplicate flag when it expires an episode from the deleted group.

It also uses an unusual message when doing so; normally, when a Deleted item expires, either due to the 7 day delay or because my drive is full, the log says:

logid: 8440

module: autoexpire

priority: 5

acknowledged: 0

logdate: 2008-05-05 11:17:38

host: pyloric

message: Expiring Program details: Expiring 308 MBytes for 1 @ Sat Jan 5 08:00:41 2008 => The

Wire "02x11: Bad Dreams"

but when it logs in this instance, it says:

logid: 7954

module: autoexpire

priority: 5

acknowledged: 0

logdate: 2008-04-28 09:26:37

host: pyloric

message: Expired program details: Expiring 507 MBytes for 1002 @ Tue Apr 15 08:59:00 2008 =>

Dora the Explorer. Too many episodes, we only want to keep 3.

Change History (1)

comment:1 Changed 11 years ago by cpinkham

Resolution: fixed
Status: newclosed

(In [21394]) Make the AutoExpirer? use the same maxepisodes logic that the scheduler uses with regard to recordings in the 'Deleted' recording group. These should not be counted against the scheduled recording's maxepisodes count since they have been Deleted.

Closes #5337. The other issues mentioned in the ticket as possibilities do not appear to be the case. The log pasted in the ticket shows the recording was deleted due to maxepisodes and that is why the erroneous message about "too many episodes" was listed.

Note: See TracTickets for help on using tickets.