Last modified: 2013-06-24 20:36:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36718, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34718 - Images not rendered correctly
Images not rendered correctly
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-25 22:09 UTC by Andre Koopal
Modified: 2013-06-24 20:36 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Andre Koopal 2012-02-25 22:09:51 UTC
At the moment it seems that thumbnails of images are not always rendered correctly. I saw some complaints popping up on nl-wikipedia so looked a bit around. For example in this article:

https://nl.wikipedia.org/wiki/%C4%BDubom%C3%ADr_Ft%C3%A1%C4%8Dnik

The image, https://commons.wikimedia.org/wiki/File:Ftacnik_lubomir_20081025_berlin_bundesliga.jpg, is not displayed. nl-wikipedia generated thumbnails in infoboxes with a default of 264px. When looking on commons, the 263px and the 265px were decently generated, but the 264px one doesn't display, not even after a purge.

The second one I saw was the map on this article:

https://nl.wikipedia.org/wiki/Xiongnu

the image being: https://commons.wikimedia.org/wiki/File:Hsiung-nu-Empire.png

Can this been looked into, it seems some caching is broken, and some broken image files are in the way or something alike.
Comment 2 Mark A. Hershberger 2012-02-25 23:26:13 UTC
Swift or the 1.19 code on commons?
Comment 3 Mark A. Hershberger 2012-02-25 23:54:18 UTC
(In reply to comment #0)
> The second one I saw was the map on this article:
> 
> https://nl.wikipedia.org/wiki/Xiongnu
> 
> the image being: https://commons.wikimedia.org/wiki/File:Hsiung-nu-Empire.png

This one seems to be a template problem as there is no reference to this file (that I can see) in the html for thd article.
Comment 5 Saibo 2012-02-26 00:34:40 UTC
(In reply to comment #4)
correct myself...

Grrr... you have only replied to the second case...  Yes, there does not seem to be a file reference inside the article...
Comment 6 Ben Hartshorne 2012-02-26 02:21:31 UTC
I think this one is an issue with the purging code, though we'll look into it more after the weekend.

I looked in both swift and ms5 (the previous and still sort-of active store for thumbnails).  Here is the list of all thumbnails there:

Swift:
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/200px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/220px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/266px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/268px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/450px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/576px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/720px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg

ms5:
-rw-r--r--     1       48       48   15447 2012-02-26 00:54 200px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
-rw-r--r--     1       48       48   18027 2012-02-25 21:51 220px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
-rw-r--r--     1       48       48   24875 2012-02-26 02:16 266px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
-rw-r--r--     1       48       48   25002 2012-02-26 00:27 268px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
-rw-r--r--     1       48       48   63989 2012-02-25 21:50 450px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
-rw-r--r--     1       48       48   97843 2012-02-25 22:13 576px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg
-rw-r--r--     1       48       48  151047 2012-02-25 22:44 720px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg

The interesting part is that there is no 264 or 265px version of this image stored there, and yet loading the URL https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/264px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg or https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/265px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg yield an error[1] and an image respectively.


[1] The image “https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Ftacnik_lubomir_20081025_berlin_bundesliga.jpg/264px-Ftacnik_lubomir_20081025_berlin_bundesliga.jpg” cannot be displayed because it contains errors.
Comment 7 Andre Koopal 2012-02-26 10:28:51 UTC
Ok, looked a bit better into the second case (I only deeply looked into the first, and the second one seems indeed something else. The first one however remains. Thanks for investigating so far.
Comment 8 Ben Hartshorne 2012-02-26 17:12:31 UTC
using curl -v to fetch the image and show the headers, I see:

< Server: nginx/0.7.65
< Date: Sun, 26 Feb 2012 17:09:17 GMT
< Content-Type: image/jpeg
< Connection: keep-alive
< Content-Length: 0
< Last-Modified: Sat, 25 Feb 2012 18:15:28 GMT
< Accept-Ranges: bytes
< Age: 31021
< X-Cache: HIT from sq53.wikimedia.org
< X-Cache-Lookup: HIT from sq53.wikimedia.org:3128
< X-Cache: MISS from sq50.wikimedia.org
< X-Cache-Lookup: MISS from sq50.wikimedia.org:80
< Via: 1.1 sq53.wikimedia.org:3128 (squid/2.7.STABLE9), 1.0 sq50.wikimedia.org:80 (squid/2.7.STABLE9)

showing that it is in squid, despite not being in swift or ms5, and that it's a 0-length file that's cached there.
Comment 9 Andre Koopal 2012-03-08 19:13:12 UTC
This specific case has closed itself, as it doesn't look structural, closing ticket now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links