Closed pianomanfrazier closed 7 years ago
Wow, how could this have been working? cc @scottpurdy @vitaly-krugl ?
Interns!! :) Hmmm... I wonder ... when MySQL is configured for no password for a given user, does it possibly ignore the password??
cc @rhyolight
@pianomanfrazier, @rhyolight: Also, the existing logic is not at all pythonic. The call to testDbConnection
returns True/False instead of raising an exception. So, even if this example test is running in CI and DB connection fails, the app would simply print a message on failure, but not communicate the failure via process exist code, so higher-level test driver has no clue that something is amiss.
Thanks Vitaly. @pianomanfrazier let me know of you want to go the extra mile as suggested, otherwise I will merge this as-is.
Well shit, I screwed up. @pianomanfrazier You are supposed to sign our contributor license before I merge. Do you mind doing that now?
Just in case, I reverted this accidental merge (all I can do at this point). @pianomanfrazier Once you sign the license I'll take care of this and get it re-merged.
Sorry for the hassle! Apparently there is something wrong with our automated contributor validator. I'll be looking into it.
Just signed the license.
Thanks, it takes a bit to process. I'll check back in later.
@pianomanfrazier I have your CL now. I'm not sure you can re-open this PR, but you can push your changes to a new remote branch and create a new PR to address @vitaly-krugl's changes.
The password is being submitted as all asterisks to the database instead of the actual password.