Running the docker tests results in an error from SQL Alchemy

[julzelements]

I've done the following:

1. Cloned the repo
2. run export PYTHON_VERSION=$(cat Pipfile | awk '/python_version/ {print $3}' | tr -d '"')
3. run docker-compose build
4. run docker-compose run dejavu pipenv run run_tests

The output is a bit too large to include, but it seems there are some errors with the sql query?

If you can point me in the right direction, I'd like to dig into this and fix/PR. Just checking with author first to see what might be obvious?

sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) operator does not exist: character varying = bytea
LINE 3: WHERE songs.file_sha1 = '\x4e56496a362f5075512b37513946374b6...
                              ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.

[bcollazo]

Oh hey, good find. I think this is from the most recent merge we did to master </3. Seems to have broken it.

Can you check if you get the same before that last merge? Further that should hint on the fix. Thanks!

[NathanielCustom]

There is something definitely going on. I'd been pulling my hair out over it the pass several days as I can't Dejavu to identify by file.

I had been playing with the build before Merge #6 and was having success. Along the way I decided to give the fork a try to see how much faster fingerprinting would be. I ran a number of concurrent tests, so in my sloppiness I lost track if I truly ever got the "speed fork" working and when things "broke".

Wondering why things all of a sudden stopped working, I spent a few days trying to troubleshoot. With no success I formatted and started afresh on two separate systems, reinstalling following my notes carefully. I was never able to get a working build with the fork or (eventually) the merge.

Tonight I downloaded Master 1.2, didn't format the OS (keeping all the modules), re-fingerprinted, and had instant success.

[julzelements]

I can confirm that checking out f113e10 [setup.py fixes]
and repeating my original steps results in zero errors.
Thanks for pointing me in the right direction. Now I have a working codebase I will start tracking this bug down. : )

[NathanielCustom]

I got Merge 5 working with no issues.