Closed hadim closed 11 months ago
For now, I simply disabled all the URI parsing logics at https://github.com/hadim/QCFractal/commits/next_hadim/qcfractal (check latest commits)
And it works fine.
Note that I also had other issues but probably more related to Cloud Run and SQL than QCF. I also had to change the URI format to db_full_uri = "postgresql://${google_sql_user.db_user.name}:${google_sql_user.db_user.password}@/${local.database_name}?host=/cloudsql/${google_sql_database_instance.db_instance.connection_name}"
@bennybp would you consider supporting full_uri without doing too much parsing on it?
I have two commits (likely not ideal) that make it work with the above sock-based URI:
Yes I am absolutely interesting in supporting that (and was one of the reasons I started putting it in. I want to be able to run via socket as well).
Let me get to this in the next few days
It took a few iterations, but the changes in https://github.com/MolSSI/QCFractal/commit/1be6db89a3e78460f67207147725c77315eaa72a should fix this.
It's probably easiest to put the host in the query string (like you had before I think. See https://github.com/MolSSI/QCFractal/blob/1be6db89a3e78460f67207147725c77315eaa72a/qcfractal/qcfractal/test_db_connection.py#L212)
See previous comment. Everything should be working with unix sockets now.
Since the parsing fails, the pydantic config becomes invalid.
Details below: