2014-01-13, 16:58
(2014-01-12, 22:09)m.savazzi Wrote:Code:2014-01-12 21:04:07.4556,EmberScraperModule.Scraper+TVImages,EmberAPI.ErrorLogger.Error,13,ERROR,"Specified cast is not valid.
at EmberScraperModule.Scraper.TVImages.Clone() in C:\Users\Massimo\Documents\GitHub\Ember-MM-Newscraper\Addons\scraper.TVDB.Poster\TVScraper\clsScrapeTVDB.vb:line 173"
Turns out this is an actual bug somewhere, but is not related to one of my changes... The specified cast is not referring to actors, but is a DirectCast call that is failing. Will look into that shortly.
I'm also changing the trace messages to be less wordy - don't need full stack trace for them!
====================
m.savazzi Wrote:I have some issues with the notifcation module and, can you check it?
The notification module that you're referring to is because I am catching attempts to load non-existant (Nothing) modules. It is a weird situation, because the master scraper routine goes through each type of scraper, and if one is defined it will call it. If none is defined for a particular type, I put in that message. Taking those messages out would quiet the logs a bit. But leaving them in tells the user what is going on when they are looking for a missing poster, only to see a WARN message of "No movie image scrapers are defined". Note that production release should only be showing ERROR or FATAL messages in the log, unless the user turns on debugging...
What do you guys think - keep those warning messages in or not? Every scrape has some undefined modules (such as the rare "generic" module")
