Open mvanotti opened 1 year ago
Sorry, I am not sure if I understood you correctly. Would removing the offending characters affect the correctness of the password?
Alternatively, we can emphasize that non-alphabetic characters are not supported for now.
The password is correct and valid (with the non-alphanumeric characters).
The problem is that the alembic
script needs to escape the url before calling create_engine
. See the SQL Alchemy docs for the explanation.
They propose two solutions: either use urllib to escape the password before setting it, or using a URL object in sql alchemy. Sadly, it seems like fuzzbench's sqlalchemy version doesn't have the URL module, so it might need to be updated first.
On top of the issue with the url quotes, the config set option uses python interpolation strings, so it fails when the password contains %
. I uploaded a PR that addresses these two issues, but needs more testing.
Thanks!
I am following the documentation for setting up a cloud project and they mention to set up a password for the sql database. I used a chrome auto-suggested password that contained non-alphabetic characters ('@', '.', and ':'), and that caused the
alembic upgrade
command to fail:It seems like the regexp used to parse the database url does not support a password with strange characters. A workaround is to remove the offending characters from the password.