ez | A Go Package for Easy , Powerful Tests and Benchmarks

I assume that when you say "If I use parentheses on that line it works", you mean that the following works as expected:

As M.Deinum said, the reason was I made my dependencies in starter "optional".

With a custom domain, you configure a DNS to point to a service, not a revision/tag of the service. So, you can't by this way.

The solution is to use a load balancer with a serverless NEG. The most important is to define the URL mask that you want to map the tag and service from the URL which is received by the Load Balancer.

This is likely to be a collation issue with the Text column in the target table.

Consider the following, which uses a Text column created with the latin1_general_ci collation:

In the integer column you're trying to add string value, try to remove default in models.

Instead of this

You've shown that you used the following code to split up a string into an list:

Try

Query does indeed have issues with mixed data types. One way to solve that is to convert everything to text..

We see what is in the output, but need to see how you actually specified the connect string in the calling application. ora-12154 is one of the most common connection issues and is written about all over the internet. What did you discover when you googled it?

It says that you specified a tns connect string that could not be located in the client's tnsnames.ora file. Since I don't know the contents of your client's tnsnames, and I don't know what you actually specified, I can't say more at this point.

However, as noted, this error is written about in just about every oracle blog and online resource on the internet. My favorite is here: https://edstevensdba.wordpress.com/2018/09/19/troubleshooting-ora-12154/

Also . . . oracle:cdb$ oerr ora 12154 12154, 00000, "TNS:could not resolve the connect identifier specified" // *Cause: A connection to a database or other service was requested using // a connect identifier, and the connect identifier specified could not // be resolved into a connect descriptor using one of the naming methods // configured. For example, if the type of connect identifier used was a // net service name then the net service name could not be found in a // naming method repository, or the repository could not be // located or reached. // *Action: // - If you are using local naming (TNSNAMES.ORA file): // - Make sure that "TNSNAMES" is listed as one of the values of the // NAMES.DIRECTORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA) // - Verify that a TNSNAMES.ORA file exists and is in the proper // directory and is accessible. // - Check that the net service name used as the connect identifier // exists in the TNSNAMES.ORA file. // - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA // file. Look for unmatched parentheses or stray characters. Errors // in a TNSNAMES.ORA file may make it unusable. // - If you are using directory naming: // - Verify that "LDAP" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Verify that the LDAP directory server is up and that it is // accessible. // - Verify that the net service name or database name used as the // connect identifier is configured in the directory. // - Verify that the default context being used is correct by // specifying a fully qualified net service name or a full LDAP DN // as the connect identifier // - If you are using easy connect naming: // - Verify that "EZCONNECT" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Make sure the host, port and service name specified // are correct. // - Try enclosing the connect identifier in quote marks. // // See the Oracle Net Services Administrators Guide or the Oracle // operating system specific guide for more information on naming.

Replace