Closed GoogleCodeExporter closed 9 years ago
Adding a catch-them-all catch block is a work around but I would like to find
the
real problem. Does the exception gets thrown for every image? Which version of
the
Python imageing library (PIL) is installed on your system?
Looking at "KeyError: '200'", a possible error reason might be, that the option
'img_type' in the player adapter configuration file accidentally has been set to
'200' (instead of "PNG" or "JPEG"). Is that the case? Then it is not a bug, but
a
misconfiguration ;)
Original comment by obensonne@googlemail.com
on 27 Nov 2009 at 8:27
It doesnt get thrown for every track. Only a small subset of them, and i havent
noticed anything common between those tracks, but I'll keep looking. I looked
in the
amarok adapter config file and couldn't find any option named img_type. Is
there any
other place that I should be looking at?
Original comment by rajivnai...@gmail.com
on 28 Nov 2009 at 3:01
Concerning the option, sorry, my mistake, this option is configured in the
client
since 0.9.2.
To debut this issue you could add some log.debug(..) calls within the
__thumbnail_img() method to see for which images and parameters the exception
occurs.
Interesting things to log are `img`, `img_type` and `img_size`.
Original comment by obensonne@googlemail.com
on 28 Nov 2009 at 11:11
Any progress here?
Original comment by obensonne@googlemail.com
on 2 Dec 2009 at 8:07
This issue was updated by revision 0b77bc9785.
Previous revision 8e8395201bd2 introduced this bug. On client size the
ClientInfo object has been initialized with the image size for the image
type value. This change fixes the wrong ClientInfo initialization.
Original comment by obensonne@googlemail.com
on 6 Dec 2009 at 6:50
Original comment by obensonne@googlemail.com
on 8 Mar 2011 at 6:38
Original issue reported on code.google.com by
rajivnai...@gmail.com
on 27 Nov 2009 at 7:18Attachments: