Currently there have been two reports of TSB ccc tagging and logging non-corrupt files as corrupt. It also appears to be storing the wrong hash value to the images, even for their thumbnail sizes. So far File:History of Carroll County, Indiana - DPLA - a7b297e0565accecf77382ce750032cf (page 457).jpg and File:Track near Tobelbach 2020-03-11 16.jpg have been affected.
Description
Description
Revisions and Commits
Revisions and Commits
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit | |
| Restricted Diffusion Commit |
Event Timeline
Comment Actions
It appears that the script is somehow saving the wrong hash values for every image. Investigating.
Comment Actions
Turns out that hashes weren't an issue and were actually the change hash....that isn't the issue here by looks.
Comment Actions
Restored activity, going to be adding more logging for corrupt images...want to know the type of errors being caught....
Comment Actions
I added logging for the specifics of the OSError triggered when corrupt images identified. Will watch the logs closely to ensure it is capturing the sort of information that I am looking for. Hopefully this leads to some useful insight if another false positive is detected.