Re: Mislabeled Hashes

From: Ben Grodsky <grodsky_at_mediadefender.com>
Date: Fri, 1 Jun 2007 11:37:34 -0700

QA always aware of their job. (Sarcasm). :(


----- Original Message -----
From: Dylan Douglas
To: Tabish Hasan; Ben Ebert; Gerald Macias
Cc: qateam; torrents
Sent: Fri Jun 01 11:34:32 2007
Subject: RE: Mislabeled Hashes

I'm working on it right now. Also, you just do a mod 137 on the entire torrent size. You don't have to do mods on every file in it.


________________________________

        From: Tabish Hasan
        Sent: Friday, June 01, 2007 11:32 AM
        To: Ben Ebert; Dylan Douglas; Gerald Macias
        Cc: qateam; torrents
        Subject: RE: Mislabeled Hashes
        
        

        Let the QA team know when things are back to semi-normal. Doing mod 137 on every file is not practical, especially since the actual avi file is sometimes not mod 137 but rather 1 of the associated files (ie the .nfo file). So we would have to do several mod 137 checks on every “real” torrent….plus all our sheets and formulas rely on us getting the hashes/torrents.

         

        ________________________________

                From: Ben Ebert
        Sent: Thursday, May 31, 2007 6:31 PM
        To: Dylan Douglas; Gerald Macias; Tabish Hasan
        Cc: qateam; torrents
        Subject: RE: Mislabeled Hashes

         

        Don’t do this manually, Dylan will work on doing it automatically tomorrow as part of fixing the hash identifier. Getting our posting numbers back up to par is more important than the hashes right now.

         

        ________________________________

                From: Dylan Douglas
        Sent: Thursday, May 31, 2007 6:18 PM
        To: Gerald Macias; Tabish Hasan
        Cc: Ben Ebert; qateam; torrents
        Subject: RE: Mislabeled Hashes

         

        That could work. I would say use the "old skool decoy" setting in the interface. The longest part would be choosing the project for each torrent file.

                 

                ________________________________

                                From: Gerald Macias
                Sent: Thursday, May 31, 2007 6:06 PM
                To: Dylan Douglas; Tabish Hasan
                Cc: Ben Ebert; qateam; torrents
                Subject: RE: Mislabeled Hashes

                Those torrents are still stored on the Torrent FTP server. Could we possibly just re-add those torrents/hashes back into the database. It may take a while but I imagine it is still is possible.

                 

                Gerald

                 

                ________________________________

                                From: Dylan Douglas
                Sent: Thursday, May 31, 2007 5:55 PM
                To: Tabish Hasan
                Cc: Ben Ebert; qateam; torrents
                Subject: RE: Mislabeled Hashes

                 

                All-

                 

                In an attempt to copy the data that the torrent team entered into the old database, I managed to wipe out the last 6 days of data. Go me! So, this means that now everything from 5/23 to 5/30 is going to say that it's real no mater what you use, since there aren't entries in the database for it.

                 

                Anything that is being tested should be checked for mod 137 to determine if it is ours or not for the next few weeks if the identifiers say it's real. (The mod 137 check, of course, doesn't need to be done if it returns that it is ours.) There is no way around this, since there is no way to get the data back.

                 

                I'm also going to make a change to the hash identifier/torrent interface that will screen out the garbage that some sites add to the torrent file (which was causing false negatives). Expect the new versions tomorrow. For now, just use the torrent interface (and stop using the hash identifier already).

                 

                -D

                         

                        ________________________________

                                                From: Dylan Douglas
                        Sent: Thursday, May 31, 2007 12:11 PM
                        To: Tabish Hasan
                        Cc: Ben Ebert; Ben Grodsky; qateam
                        Subject: RE: Mislabeled Hashes

                        Q: Dan asked what caused case 1.

                        A: Some data was entered into the old database by Rendy and Gerald (they must have been using the old version of the interface). I am going to do another dump from the old database to the new database for several tables (should only take a couple hours.) Will email when the dump is finished.

                         

                                 

                                ________________________________

                                                                From: Tabish Hasan
                                Sent: Thursday, May 31, 2007 11:06 AM
                                To: Dylan Douglas
                                Cc: Ben Ebert; Ben Grodsky; qateam
                                Subject: RE: Mislabeled Hashes

                                Oh ok, we can wait for the new version…

                                But these errors are caused by the torrent interface that’s supposed to point to the correct DB. We’re not just seeing errors with the QA hash identifier.

                                 

                                ________________________________

                                                                From: Dylan Douglas
                                Sent: Thursday, May 31, 2007 11:02 AM
                                To: Tabish Hasan
                                Cc: Ben Ebert; Ben Grodsky; qateam
                                Subject: RE: Mislabeled Hashes

                                 

                                T-

                                 

                                I sent an email last week to Dan that, I think, was CCed to the QA team saying not to use QA's torrent hash identifier until I had a chance to update it. The work around was to get the torrent interface, since that is pointing to the correct database.

                                 

                                I will make a new version of the hash identifier today and email QA team when it is ready.

                                 

                                -D

                                         

                                        ________________________________

                                                                                From: Tabish Hasan
                                        Sent: Wednesday, May 30, 2007 6:58 PM
                                        To: Dylan Douglas
                                        Cc: Ben Ebert; Ben Grodsky
                                        Subject: FW: Mislabeled Hashes

                                        Dylan,

                                         

                                        The hash identifier is reporting the hashes incorrectly and reporting some errors. See below for details.

                                         

                                        -TH

                                         

                                        ________________________________

                                                                                From: Jonathan Perez
                                        Sent: Wednesday, May 30, 2007 6:14 PM
                                        To: Tabish Hasan
                                        Cc: qateam
                                        Subject: Mislabeled Hashes

                                         

                                        Here are the mislabeled hashes that I found on the Universal Pictures 5-29-07 torrent results. Also currently getting a “Database query error! (0x100B) bt_generator_maininfo” error when trying to check hashes in the BT Interface.

                                         

                                        1: Marked as Real by the BT Interface but marked as Old Skool in the Hash Identifier

                                        8fe9d5272f54a63bbe047f3e03ac772f76f79540

                                        8fe9d5272f54a63bbe047f3e03ac772f76f79540

                                        1e096f8e9c40ab5d75ed6c4fe982097f299c2a72

                                         

                                         

                                        2: Marked as Real by the Hash Identifier but marked as Old-Skool by the BT

                                        Interface.

                                        1f55891ed62cf6653fa92304ccf53132415242a2

                                        c49afb455dea5d90a39a24a83915ea706df8bece

                                        87dee391785a9e17573aac28d9b8d7938c3ad19a

                                        1f55891ed62cf6653fa92304ccf53132415242a2

                                         

                                         

                                        3: Marked as Real by the Hash Identifier but marked as Regular Decoys by the BT

                                        Interface.

                                        44acff695ecbdf717ee92fd1874c0c24191a5de3

                                        778c80cf75da425c47e440978b47809cf1cb7305

                                        fe8a2ebb37f01c9af099426d2f7cebf0efd38aae

                                        c17adaf8019fa159ac54c45a845e6ebe4c945561

                                        55eb68ed696085df366d4c434a7469c28d0106ee

                                        ee0b741ddd9e8cf3d744fab902bda8b9f967f4ae

                                        7ad234328253e30547c2ede95b7c870ba8227630

                                         

                                        4: Marked as Real by the Hash Identifier but marked as 90% Decoy by the BT Interface

                                        85136d02e3d7795dd704643b6a9216e63f01fbfc

                                        c9331cbfcf92e172aa8ba7fbc9c2280839830ece

Received on Fri Sep 14 2007 - 10:55:58 BST

This archive was generated by hypermail 2.2.0 : Sun Sep 16 2007 - 22:19:47 BST