{"push_id":865520417,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"e5ae6a2cd62c4508f78b5e29e2d67575f1071077","before":"141266881330eaaada0847860a3b1092a082e2b4","commits":[{"sha":"9636e5353746eb66caac7912351b615cb2cc0a1e","author":{"email":"336d06a97d2c99073ae54ac27c7ae967c7448c86@users.noreply.github.com","name":"Tobias Blomberg"},"message":"Fix a few uninitialized variable Coverity warnings","distinct":true,"url":"https://api.github.com/repos/sm0svx/svxlink/commits/9636e5353746eb66caac7912351b615cb2cc0a1e"},{"sha":"e5ae6a2cd62c4508f78b5e29e2d67575f1071077","author":{"email":"336d06a97d2c99073ae54ac27c7ae967c7448c86@users.noreply.github.com","name":"Tobias Blomberg"},"message":"Fix Coverity scan issue 153979, calling risky function\n\nCoverity scan will warn for uses of \"rand\" since it's not wise to use\nthat function in security related contexts. In this case however it was\nused to generate noise, so it wasn't a bug really. Changed the call to\nrand_r which Coverity scan does not complain about, even if it's the\nsame thing. It's better to use rand_r anyway since it's thread safe.","distinct":true,"url":"https://api.github.com/repos/sm0svx/svxlink/commits/e5ae6a2cd62c4508f78b5e29e2d67575f1071077"}]}