wish of those help I think it is a tie between the underscore '_' and camel case - or capitalization as you call it. Hyphen gets interpreted as an operator in many languages, so it should be avoided as a common naming tool. All languages I have used (fortran, pascal, C/C++, Java, PHP, JS, Python) all differentiate and accept capitalization and underscores in variable names. So, it becomes a matter of preference. I was taught camelCase through school so that is what I have stuck with. It creates a bit shorter variable name than inserting underscores and is easier to type. Having said that, I think names with underscores are a bit more readable, and that is reason enough to use them over others. If I could get my brain to change it's habits, I would use underscores.
bigquery: Loading "DATE", "INT64" and "FLOAT64" types not supported?
With these it helps DATE is still rolling out through our stack. Support for using this type in load jobs was checked in yesterday and will hopefully be out in production next week. FLOAT64 and INT64 are currently understood only in the standard SQL query language. For load jobs, please continue to use FLOAT and INTEGER for now (they're equivalent to the 64 versions in standard SQL).
"APK Signature Scheme v2" is supported only by "apksigner" not by "jarsigner"
To fix the issue you can do Yes, you'll need to switch away from jarsigner. jarsigner is for signing JAR files. Thus, I don't believe jarsigner will ever support APK Signature Scheme v2 -- it just would not make sense. You'll need to use apksigner or other tools which support APK Signature Scheme v2.
"logs" command is supported only for "json-file" and "journald" logging drivers (got: gcpl