Closed GoogleCodeExporter closed 9 years ago
Thanks for the (refreshingly complete!) bug report.
A few questions:
Did you mean to type 1.0.16 and not 1.0.6?
Does this problem happen with any comic book that you scrape, or just Action
Comics 887?
There's a couple of things you could try that I recently described for someone
else
who was having trouble:
http://comicrack.cyolito.com/user-forum/32-news-and-announcements/7360-comic-vin
e-scraper-1022#7375
In particular, I describe how you can get a debug log when running comic
rack--if
that log contains anything in it, it could really help me track down the cause
of the
problem that you are experiencing.
Original comment by cban...@gmail.com
on 4 May 2010 at 4:17
No, funny enough I do mean 1.0.6. It took me a while to get round to
upgrading. I
have tried about 15 - 20 comics. Same results. All of them are ones that
worked
with my old version of comic scrape. I will look at the link tonight and let
you
know. Thanks! Great script BTW, thanks for all the time and effort you put
into it.
Original comment by cdkn...@gmail.com
on 4 May 2010 at 4:28
Ah, 1.0.6, eh? That gives me hope that one of the things I suggest in the link
(deleting the Comic Vine Scraper user data) will permanently solve your
problem.
Also, make extra sure that you are using the version of ComicRack that you
think you
are (i.e. the latest version, 0.9.122.) If memory serves, there was a fairly
big
change to ComicRack at one point a while back, so I wouldn't expect 1.0.6 to
work at
all with the most recent Comic Rack (though I'm not positive about that.)
I'm happy to hear that you're finding the script useful (aside from this bug!)
Let
me know how things go.
Original comment by cban...@gmail.com
on 4 May 2010 at 4:37
Just double checked 0.9.121 is what I am running and the only one I can find as
per
this link: http://comicrack.cyolito.com/downloads although the homepage does
mention a 122 running on Win7. and the script was 1.0.6 just did American
Vampire
and it worked fine. I will try your link tonight though and see what I can do.
Bugs are a nasty essential step toward progress so no biggie! Haha
Original comment by cdkn...@gmail.com
on 4 May 2010 at 4:54
OK, So this is weird. I blew out everything just as your link said. Loaded it
all
back up. Same problem. Invoked the switches to get the script dump and . . .
. No
Failure! Weird. So I closed the program and re-opened it without the script
dump .
. . Fail. Turned the script dump back on . . . Fail. Couldn't get to the error
because ComicRack was locked and that window must me attached . . . couldn't
bring it
into focus. Unbound the all the windows with "reader in own window" option and
set
everything so I could see the output window in the case of another abend. No
failure. Put everything back . . . now windows bar with close minimize etc
stayed
persistant (with the new version of ComicRack I had noticed that the standard
windows
bar at the top had gone away, after I re-bound everything it came back) . . . no
failure. I can't get the error to come back. In short . . . I have nothing
else to
give you but everything seems to be working again. Very odd.
BTW . . . the new version of the script is AWESOME! Sorry, I can't give you
more to
go on. Not even sure this can be classified as a bug anymore. Very odd. Glad
it's
working though. Sorry to take up your time.
Original comment by cdkn...@gmail.com
on 4 May 2010 at 11:30
Well, at least it's working for you now, and I'm glad you like the new
version--there's definitely been a lot of changes since 1.0.6!
I'm somewhat concerned that you might be experiencing an on-and-off bug related
to
the way I do windows and graphics threads. I think I'll leave this bug report
open
for a little while, and maybe you can let me know if you see this problem
again? If
I don't hear from you for a while, I'll eventually close the bug report.
That debug window text (when the scraper fails) will be super valuable, so if
you do
see this bug start to happen again, I'd still really appreciate a copy of that
log if
you can manage to get one.
Then again, it would also be cool if nobody ever sees this problem again. :)
Original comment by cban...@gmail.com
on 5 May 2010 at 2:16
Have you seen this bug show up again? If everything's been working fine for
you, I think I'll close this bug now.
Original comment by cban...@gmail.com
on 21 Jun 2010 at 11:16
Original comment by cban...@gmail.com
on 4 Jul 2010 at 10:28
Original issue reported on code.google.com by
cdkn...@gmail.com
on 4 May 2010 at 10:41