Unable to connect ... continue scanning? (with debug log)

you have the code, do the changes you want. we won't.

So, let me see - anything that XBMC/Scraper trip over, you are going to pop the message "Unable to connect to the server"?

Nice. Positive. Really constructive & productive. Not arrogant at all, not one bit. Truly in the spirit of what you guys (used to) stand for.

jhsrennie Wrote:The problem appears to be that XBMC is failing to construct the search request to themoviedb.org properly. Both problems seem to be with .rar files.

I'm not going to pursue this myself, but maybe the devs would like a copy of the offending rar, or some details.

I've be inclined to unpack and repack the two offending rars, Juan_Martnn_-_La_Guitarra_Flamenca.part01.rar and ppv7-8.part1.rar and repack them just in case there's some oddity with the rar.

JR

Are the rar files password protected ?

This feature/behavior was requested multiple times and as spiff said, we were sick of requesting debug logs just to tell the users the website is down.

do you have any idea how few of our users would even know they have a log avail, yet alone would utilize it? we do. having this dialog there has saved us TONS of time, time much better spent coding and improving the application.

also; the text has been changed since i added the dialog. i specifically used the string 'Error communicating with the server. This may indicate that the backend is down. Continue scanning?' (or thereabout) because i knew there could be false positives.

i will gladly tell you how to disable the dialog in code if you want to. but we will NOT re-add this to our already large support load.

@CrashX: They were not. Nor were they corrupted. After I looked at log, spotted the same as jhsrennie, I simply deleted the .rars because keeping them was not necessary - media files were already extracted and perfectly playable.

@vdrfan: As per attached log, the scraper site is not down. Scraping failed on those two out of hundreds of folders.

@spiff: I do appreciate the offer. It is easier for me though to deal-with offending files and folders than run my own compiles. C'mon, meet me 1/2 way - how about adding the on-off switch for this specific Dialog in advancedsettings? Make it "ON" by default, no problem, just allow the minority (apparently) that can read the log to be able to switch it "OFF"?

in accordance with our new, arrogant, nonproductive and nonconstructive spirit the option has been added in r32913.

In the spirit of humility, forgiveness, understanding, peace on Earth and everything else soft and cuddly... I thank you, most sincerely. If I could award you a medal... I would.

fdlsys Wrote:Don't you get grumpy with me, Grumpy

So the solution is to intentionally lie to the user that it's the "server fault" even though it's blatantly obvious, even without looking into the log, that is not the case!?! You are not doing a favour to anyone...

Write the LOG, that's what it's for! Let the scraping go on! Geez...

I would vote for XBMC displaying the error. After all, the problem was something to do with those rars and the user needs to know about it. Even if the problem was just the web server response I'd still vote for it to be flagged to the user for the reasons spiff mentions.

The error could be more tidily handled. The cause of the error was XBMC failing to construct the search URL properly and an error could be flagged at this point rather than waiting for themoviedb to respond badly to the bad search URL.

If the error can be reproduced on a developer's PC then I imagine a developer somewhere would be interested in fixing it.

JR

fdlsys Wrote:In the spirit of humility, forgiveness, understanding, peace on Earth and everything else soft and cuddly... I thank you, most sincerely. If I could award you a medal... I would.

Code:

<videoscanner>
  <ignoreerrors>true</ignoreerrors> <!-- Set to true to silently ignore errors while scanning videos
</videoscanner>

Agreed, this is just awesome since I started getting these errors when I started using MySQL-database.