Unexpected Error

[GoogleCodeExporter]

DESCRIBE THE PROBLEM:

An Unexpected Error Occured

WHAT STEPS WILL REPRODUCE THIS PROBLEM? (Please include the exact name of
the eComic book that you were trying to scrape, if possible.)
1.Scrape any comic. Strart scraping.
2.Comiccover view pops up.
3.Error pops up, no scrape.

WHAT VERSION OF COMICVINESCRAPER ARE YOU USING?
Was happening in .24 upgraded to .25 and it's happening there as well.

Original issue reported on code.google.com by mr.carver on 27 Jun 2010 at 12:23

Attachments:

• error

[GoogleCodeExporter]

Thanks for the bug report (and the error log).

Does this happen every single time you scrape any comic, or is it something 
that just happens now and then?   

I just tried the exact same scrape on my computer (using the information in the 
log you provided) and it worked without any problem.   So there's likely 
something different about your computer, we just need to figure out what that 
is.

The first idea that occurs to me is that something like a firewall or router is 
somehow blocking your access to comicvine website.  To test that theory, try 
visiting this link with your web browser:

http://api.comicvine.com/search/?api_key=4192f8503ea33364a23035827f40d415d5dc5d1
8&format=xml&limit=20&resources=volume&field_list=name,start_year,publisher,id,i
mage,count_of_issues&query=2000%20ad&offset=0

When I go there, I get an xml listing, i.e. a very long document where the 
first three lines are: 

<response>
<error>OK</error>
<limit>20</limit>

Is that what you get, or do you get some kind of an error page?

Original comment by cban...@gmail.com on 27 Jun 2010 at 4:54

• Changed state: Accepted

[GoogleCodeExporter]

was a temp problem on CV's side it appears. Issue is gone. The only really odd 
thing about this now would be the log itself, which states .24 as the version 
used, when it was actually .25

(also oddly, the issue in the log was not the issue being scrapped)

Original comment by mr.carver on 27 Jun 2010 at 6:28

[GoogleCodeExporter]

Yes, it probably was a problem with CV, since I think the error you got might 
have been a result of their server returning unexpected data.   

Glad it is has sorted itself out (my favourite kind of bug.)

Original comment by cban...@gmail.com on 28 Jun 2010 at 5:52

• Changed state: WontFix