[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Aaron Schulz changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #15 from Aaron Schulz --- *** Bug 17070 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Aaron Schulz changed: What|Removed |Added CC||azat...@gmail.com --- Comment #14 from

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Nemo_bis changed: What|Removed |Added CC||bhartsho...@wikimedia.org,

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #13 from Aaron Schulz 2012-03-28 17:29:34 UTC --- A race condition involving a lack of locking was fixed (which previously allowed mixed up metadata for two rows). -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cg

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Mark A. Hershberger changed: What|Removed |Added Blocks||34755 -- Configure bugmail: htt

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #12 from Aaron Schulz 2012-02-29 22:50:23 UTC --- (In reply to comment #11) > We can now fix this for individual broken cases as of r54328. Underlying cause > of why they're wrong might need fixing still? More script updates in r1

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Platonides changed: What|Removed |Added Keywords||shell -- Configure bugmail: https://bugz

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Jimmy Xu changed: What|Removed |Added Blocks||23529 -- Configure bugmail: https://bugzil

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Guillaume Paumier changed: What|Removed |Added CC||gpaum...@wikimedia.org

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Chad H. changed: What|Removed |Added CC||innocentkil...@gmail.com --- Comment #11

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #10 from Aaron Schulz 2009-07-27 08:32:05 UTC --- (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #5) > > > populateSha1 wouldn't fix anything, since it only works on files which > > > don't > > >

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #9 from MZMcBride 2009-07-27 08:26:32 UTC --- (In reply to comment #8) > (In reply to comment #5) > > populateSha1 wouldn't fix anything, since it only works on files which don't > > have hash in the db. These files do have a

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #8 from Aaron Schulz 2009-07-27 05:41:45 UTC --- (In reply to comment #5) > populateSha1 wouldn't fix anything, since it only works on files which don't > have hash in the db. These files do have a hash, although it's wrong.

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #7 from Platonides 2009-07-26 22:38:09 UTC --- I don't think so. It's simply that the hash wasn't expected to be wrong. But note that sometimes the wrong hash is on an old image version. So you would need to iterate all image

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #6 from MZMcBride 2009-07-26 22:06:02 UTC --- Why not just make ?action=purge re-calculate the hash? Is it too expensive or something? -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email --- You

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #5 from Platonides 2009-07-26 22:00:47 UTC --- populateSha1 wouldn't fix anything, since it only works on files which don't have hash in the db. These files do have a hash, although it's wrong. -- Configure bugmail: https:/

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Aaron Schulz changed: What|Removed |Added CC||jschulz_4...@msn.com --- Comment #4

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 --- Comment #3 from Platonides 2009-02-04 23:53:56 UTC --- I have been studying the hashes of commons images. The errors can be sorted very clearly. There're images where the hash of an older version got 'stuck'. The image sha1 wasn't upd

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Brion Vibber changed: What|Removed |Added Blocks||16660 --- Comment #2 from Brion Vib

[Bug 17057] Images with wrong SHA1

https://bugzilla.wikimedia.org/show_bug.cgi?id=17057 Platonides changed: What|Removed |Added CC||platoni...@gmail.com Summary|