Feature Request - log file additions

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
Post Reply
HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

Feature Request - log file additions

#1

Post by HTBruceM » Mon Mar 07, 2016 4:07 pm

I have the following suggestions to include in the LOG file. Most of these are intended for future debugging by the developer and users as the tool matures.

1) Output the EPG123 version number into the log file.
2) Output the EPG123 configuration options that were in effect at the time of execution. Users can change the configuration of EPG123 at any time; this would identify if the user has changed anything from the last run.
3) Add the same content that is sent to STDOUT in the two console shells that come up. This should also include the name of the listing(s) being requested, quantity of channels/listings etc. on each run. Seems like good history to have.

glorp

Posts: 354
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#2

Post by glorp » Mon Mar 07, 2016 4:16 pm

+1, and if possible:

4) write an update run start and update run finish (with success/failure code or flagged as info/error event) message to Windows Applications and Services/Media Center Event Log

I also see these from 0.7.5 which I assume are not really errors but just some info from SD during the development cycle

Code: Select all

[3/7/2016 7:30:01 AM] [ERROR] epg123 is not recognized as an approved app from Schedules Direct. code: 1005 , message: Did not recognize the submitted client. , datetime: 2016-03-07T15:30:01Z

User avatar
garyan2

Posts: 5196
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#3

Post by garyan2 » Mon Mar 07, 2016 7:27 pm

glorp wrote:+1, and if possible:

4) write an update run start and update run finish (with success/failure code or flagged as info/error event) message to Windows Applications and Services/Media Center Event Log

I also see these from 0.7.5 which I assume are not really errors but just some info from SD during the development cycle

Code: Select all

[3/7/2016 7:30:01 AM] [ERROR] epg123 is not recognized as an approved app from Schedules Direct. code: 1005 , message: Did not recognize the submitted client. , datetime: 2016-03-07T15:30:01Z
Planned to do 1 & 2, number 3 is scattered in the log file already, and 4 is a good idea. I'll work on that.

The ERROR being recorded is expected right now since I haven't arranged with SD on the proper version. Wasted energy right now considering rate of new releases.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

Post Reply