https://bugzilla.wikimedia.org/show_bug.cgi?id=53770
--- Comment #20 from Bawolff (Brian Wolff) <[email protected]> --- (In reply to Bawolff (Brian Wolff) from comment #19) > (In reply to Andre Klapper from comment #5) > > Aaron: As long as this is "fresh", could you take a look at this? > > > > For > > https://commons.wikimedia.org/wiki/File:Rue_G%C3%A9n%C3%A9ral-Nouvion.JPG I > > don't see the thumbnail rendered for the old revision, and clicking that old > > revision says "404 Not Found - The resource could not be found. > > Regexp failed to match URI: "/wikipedia/commons/archive/5/59/" ". > > I believe the broken old version of the file is caused by (the now fixed) > bug 54736 (Since it has mising archive name, exact same timestamp as other > version, and was uploaded by upload wizard). I probable conjecture is that > the broken nature of this file is preventing other actions to happen to this > file, as a safety precaution when the code notices that it cannot > succesfully move/delete/etc the file, so it doesn't do anything to prevent > the translation of an inconsistent state/unknown state into a further data > loss state. Maybe. That's just a guess with no checking or evidence to back > it up. Testing this theory, I tried locally creating a file that would have bad database entries similar to what bug 54736 would cause (via just adding a dummy oldimage entry without an oi_archive_name), to see if moving/deleting is affected. However I could still move/delete my test file just fine. So no go on that. However it could be that either the physical files are messed up, or that different code paths are executed when using swift vs when using normal file system image backend (like my local wiki uses) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
