{"push_id":2469817300,"size":1,"distinct_size":1,"ref":"refs/heads/tickets/DM-14040","head":"1aff93bbde4f680d09d12181e21bc1f2f9b4808d","before":"840d4a3083473ff9ff98a3f8de07f3d9138bd580","commits":[{"sha":"1aff93bbde4f680d09d12181e21bc1f2f9b4808d","author":{"name":"Fritz Mueller","email":"510a0fa183e48ad53091e028d77662598b878009@slac.stanford.edu"},"message":"Fix integration test worker crash for MariaDB 10.2\n\nUnder MariaDB 10.2.14, the MYSQL_FIELD def_length field is sometimes\ncoming back garbage (bignum), causing a std::string ctor below to\nblow up.\n\nMySQL docs say this field and its partner are not set unless this\nMYSQL_FIELD comes back from a call to mysql_list_fields(), which is\nnot the case in our call chain. Perhaps this field happened to be\ninit'd or harmless in previous versions of MariaDB, but it seems no\nmore...\n\nRemoved the default-value machinery from sql::Schema, as it was\nthus never correct and was not being used.  Deprecated corresponding\nfields in the ColumnSchema protobuf message.","distinct":true,"url":"https://api.github.com/repos/lsst/qserv/commits/1aff93bbde4f680d09d12181e21bc1f2f9b4808d"}]}
{"actor":{"display_login":"fritzm"}}