[mythtv-users] Delete + Rerecord

[Karl Newman]

On Thu, Jul 17, 2014 at 1:49 PM, Karl Newman <newmank1 at asme.org> wrote:

> On Thu, Jul 17, 2014 at 1:36 PM, Hika van den Hoven <hikavdh at gmail.com>
> wrote:
>
>> Hoi Michael,
>>
>> Thursday, July 17, 2014, 9:16:12 PM, you wrote:
>>
>> > On 07/17/2014 03:05 PM, Karl Newman wrote:
>> >> On Thu, Jul 17, 2014 at 11:58 AM, Michael T. Dean wrote:
>> >>
>> >>> On 07/17/2014 02:51 PM, Karl Newman wrote:
>> >>>
>> >>>> Thanks, Paul. Mythweb uses DELETE_RECORDING as well (and the
>> recording is
>> >>>> successfully deleted), but then follows it with FORGET_RECORDING.
>> Looks
>> >>>> like the code just needs to be changed to add the "FORGET" parameter
>> to the
>> >>>> DELETE_RECORDING command. So it looks like that should be an easy
>> fix, but
>> >>>> I don't see any replacement for FORGET_RECORDING, so the "Forget Old"
>> >>>> button in mythweb won't work without deleting the recording. Not
>> ideal.
>> >>>>
>> >>> FORGET_RECORDING should still work.  Delete followed by forget is
>> fine,
>> >>> too (assuming forget works), so MythWeb wouldn't need to change to
>> use the
>> >>> delete command with the forget argument.
>> >>>
>> >>> If FORGET_RECORDING is broken, time would be best spent fixing it
>> instead
>> >>> of putting a workaround inside MythWeb (especially if that workaround
>> only
>> >>> works when also deleting a recording).
>> >> Thanks, Mike. I spoke too soon--I just saw that FORGET_RECORDING is
>> still
>> >> part of the protocol. Probably mythweb is invoking it incorrectly.
>> I'll see
>> >> if I can figure out what the backend is expecting and get Mythweb to
>> pass
>> >> the correct parameters.
>>
>> > A wild guess would be that one side or the other (most likely the
>> > MythWeb side) may not have been properly updated after the UTC changes?
>> > Or perhaps something with the recordedid changes?
>>
>> > Mike
>> > _______________________________________________
>> Now the right list.
>>
>> I can state I have never seen it working in mythweb. If I have a show
>> marked as previously recorded, I have to force it with record anyhow
>> I run 027.1. through Gentoo
>>
>>
>> Tot mails,
>>   Hika                            mailto:hikavdh at gmail.com
>>
>
> That's my recollection too, Hika--I've never seen the "Forget Old"
> working. @Mike, I think the UTC stuff got all updated in Mythweb. I haven't
> seen any other UTC related issues, and it's just pulling from the database
> (which is UTC) as far as I can see, so theoretically telling it to forget
> an old recording should just be regurgitating what it pulled from the
> database, but possibly it's doing it with some
> wrong/corrupted/mis-formatted information. Is there some detailed backend
> logging for this which could tell us why it's failing to forget the
> recording?  Presumably it's something in the identifying information passed
> as an argument to FORGET_RECORDING that's not matching.
>
> Thanks,
>
> Karl
>

Following up on this issue. I poked around the code base a little bit and
discovered that FORGET_RECORDING is not a command that is apparently used
by the frontend which means it's a dark corner of the code that may not
have been tested recently. It does show up in the python bindings, however,
so before I go spelunking in the mythweb code trying to figure out if the
mile-long arguments to FORGET_RECORDING are correct, I'd like to play with
the same function in a python script to see if it works there. If it
doesn't work it could be a backend issue. Can anyone point me to a simple
python script example that uses the FileOps binding object so I can test
its forgetRecording method?

Thanks,

Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140729/9abaf687/attachment.html>