Opened 12 years ago

Closed 20 months ago

#10036 closed Bug Report - General (Trac EOL)

Auto MetadataLookup doesn't always run

Reported by: doug@… Owned by: Raymond Wagner
Priority: minor Milestone: needs_triage
Component: MythTV - Mythmetadatalookup Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no



I record "Little Einsteins" from 6:30-7am and 7-7:30am every day. The rule has an Auto MetadataLookup? Job and a Auto User Job. The first recording always runs the MetdataLookup? and the User Job. The second one runs the User Job but the MetdataLookup? never runs. My theory is that something gets confused since the same show is being recorded back to back and the User Job is still running when the new show starts but I'm not sure.


Change History (6)

comment:1 Changed 12 years ago by Doug Haber <doug@…>

I think the issue here is that init_jobs() doesn't get called if the same show is recorded back to back. Without init_jobs, the auto metadatalookup doesn't get called. I'm guessing it has something to do with the scheduled event not changing from "None to RecordingOnly?" but staying as "RecordingOnly? to RecordingOnly?". I'm not sure why this only happens when the same show is recorded back to back.

comment:2 Changed 12 years ago by Raymond Wagner

Component: MythTV - GeneralMythTV - Mythmetadatalookup
Owner: set to robertm
Status: newassigned

comment:3 Changed 12 years ago by robertm

Owner: robertm deleted
Status: assignednew

Since this doesn't appear to have anything to do with code I've written, but rather with the jobqueue (and because I can't reproduce) I am unassigning.

comment:4 Changed 10 years ago by Raymond Wagner

Owner: set to Raymond Wagner
Status: newaccepted

comment:5 Changed 3 years ago by Stuart Auchterlonie

Milestone: unknownneeds_triage

comment:6 Changed 20 months ago by Stuart Auchterlonie

Resolution: Trac EOL
Status: acceptedclosed

We have moved all bug tracking to github [1]

If you continue to have this issue, please open a new issue at github, referencing this ticket.

[1] -

Note: See TracTickets for help on using tickets.