{"push_id":1427848960,"size":2,"distinct_size":2,"ref":"refs/heads/2.0","head":"38e4a5902f81527c2b85c4011c8071b8a0fd9d39","before":"cc54d80a8b7811da06ddeb40c2402f957441eb1f","commits":[{"sha":"9ede657a9bc5c24f964d065e2cfaa429008c19ec","author":{"name":"ekorh475","email":"c50f24d96a8f536ca38b641fda0fe22be5e0cd97@users.noreply.github.com"},"message":"Change error message when permissions on .secrets are wrong\n\nIf the user running MaxScale could open the .secrets-file and the\nfile permissions were anything other than owner:read, the\nsecrets_readkeys() would fail with error message\n\"Ignoring secrets file <path>, invalid permissions.\" Now the\nmessage is more accurate in stating the expected permissions.","distinct":true,"url":"https://api.github.com/repos/mariadb-corporation/MaxScale/commits/9ede657a9bc5c24f964d065e2cfaa429008c19ec"},{"sha":"38e4a5902f81527c2b85c4011c8071b8a0fd9d39","author":{"name":"ekorh475","email":"c50f24d96a8f536ca38b641fda0fe22be5e0cd97@users.noreply.github.com"},"message":"MXS-576 Check for negative values for config settings\n\nPreviously, negative values were allowed for persistpoolmax and\npersistmaxtime. Now they cause an error. Also, monitor_interval\nallowed negative (or zero) values, which were then implicitly cast to\nunsigned, causing unintended behaviour. Now this causes a warning\nand the default value is used.","distinct":true,"url":"https://api.github.com/repos/mariadb-corporation/MaxScale/commits/38e4a5902f81527c2b85c4011c8071b8a0fd9d39"}]}
{"actor":{"display_login":"ekorh475"}}