https://bugzilla.wikimedia.org/show_bug.cgi?id=16732


Roan Kattouw <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]




--- Comment #1 from Roan Kattouw <[email protected]>  2008-12-21 00:20:40 
UTC ---
(In reply to comment #0)
> I have a list of images gathered on the last month, via the API allimages
> generator. It should be ordered, and it is, however a few percentage of the
> images (quite noticeable on the full list) is wrongly order such as
> Ayutthaya_Elephant_Camp.JPG before Ayun_Halliday_by_David_Shankbone.jpg or
> Basketball_29082008666_(6).jpg followed by Basiliscus_vittatus-2.jpg
> 
> The fault could be on three places: my program, the API or the slave.
> 
> My program doesn't do any reaordering, the list is dumped in the same order as
> received from the connection. It can produce unordered lists if it is run,
> stopped and run again from a previous point. But it doesn't explain jumps as
> going from Auto_Racing_Yellow.svg to Image* (ImageAKMap-doton-Amukta.png,
> ImageAerienneRafRaf.JPG, ImageAlumbrados_del_Rio-2007_Medellin.jpg,
> ImageBrute.jpg, ImageBunnygirl_Cosplay2.jpg, ImageCBCdecryptie.jpg,
> ImageCBCencryptie.jpg, ImageCFBencryptie.jpg, ImageCapendu.PNG) and back to
> Auto_Racing_Yellow_Chevron.svg (continuing in alphabetical order).
> 
If your program somehow messes up aicontinue values, such things could happen.
The Auto-Image-Auto bug looks like some weird race condition or improper
handling of parallel requests.

> As the list is built from many API queries, there can be many servers serving
> it, and multiple race conditions. However, it happens to images uploaded many
> months ago, if not years. So it's not a lagged slave nor a new image uploaded
> between. And I don't know on any locale which would do such misorderings.
> 
Of course image creations/deletions don't explain huge jumps.

> I can provide the app/files, but they're huge, and not too useful.
> 
The only useful information you could provide is an example of an API request
that returns a wrongly ordered list. If you manage to find one, please REOPEN
this bug.

A debugging hint: let your program log all its API requests (parameters,
response, timestamp) to a separate log file. Then run it again, and if it
orders your images wrongly again, examine the log to see what went wrong.

Closing as WORKSFORME (because, well, it does).


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to