Feature Request - log file additions

An evolving, supported alternative to Rovi
Important Information
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf

Feature Request - log file additions

Post#1 » 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.
HTBruceM
 
Posts: 87
Joined: 22 December 2012
Location: Oregon
HTPC Specs: Show details
5+ YrsTGB Veteran

Post#2 » 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
glorp
 
Posts: 319
Joined: 23 September 2012

Post#3 » 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.
User avatar
garyan2
 
Posts: 2158
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net


Return to EPG123



Who is online

Users browsing this forum: No registered users and 3 guests

cron