{"push_id":781289198,"size":1,"distinct_size":1,"ref":"refs/heads/mr4.0","head":"0e06afe6dc78e779d4fe16ec9c51fa9d4732236e","before":"cbd8720140c12f36c62c44c22999bf08b77e83e6","commits":[{"sha":"0e06afe6dc78e779d4fe16ec9c51fa9d4732236e","author":{"email":"720c34b0c269bd91e5a3ed0b49f5fedf81ba606a@sipwise.com","name":"Rene Krenn"},"message":"MT#14317 passing now() to interval catchup and resize\n\nformerly, the contract_balance catchup (and resize) procedures\nused contracts.modified_timestamp, whose value was intended to\nbe set explicitly upon update operations.\n\nit turns out that mysql ON UPDATE current_timestamp columns\neffectively ignore the explicit timestamp value, unless it\nexactly matches the old timestamp value.\n\nwhile this is not an issue for the logic in production usage,\nthis seems to be the reason why the api-balance_intervals.t test\nfails occassionally with its time-warp cases.\n\nChange-Id: I504dd98548b88c99079e071598806d884c4422eb\n(cherry picked from commit c7b3d74a21fc6656b850c44e9f8b2359b09b2c8e)\n\nConflicts:\n\tlib/NGCP/Panel/Utils/ProfilePackages.pm","distinct":true,"url":"https://api.github.com/repos/sipwise/ngcp-panel/commits/0e06afe6dc78e779d4fe16ec9c51fa9d4732236e"}]}