{"push_id":1592406515,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a3d396753f61574b4a0a0d5b13a48c48f3976b32","before":"84e678086d32c72ce52104d4b1d0f2150469cf80","commits":[{"sha":"a3d396753f61574b4a0a0d5b13a48c48f3976b32","author":{"name":"Kambiz Aghaiepour","email":"28ba2c7c8d890d70dcbf2738bdd84976e5780a00@redhat.com"},"message":"Logic error in computing schedule index\n\nThere is currently a logic bug in lib/quads.py that makes some\nassumptions that the next available assignment id will always\nbe iterative. This can be triggered when a schedule has been\nremoved and another net-new schedule is added. This is a serious\nissue that can cause disruption/reprovisioning of an existing\nenvironment.\n\nThe length of the array of keys in the schedule dictionary was\nassumed to be the correct next index.  This assumption breaks\nwhen a host has schedules that were removed.\n\nThis hot-fix corrects this problem.\n\nFixes: https://github.com/redhat-performance/quads/issues/35\n\nChange-Id: I7bc87cd4b42c222954215c334e4de4e97fca0e93","distinct":true,"url":"https://api.github.com/repos/redhat-performance/quads/commits/a3d396753f61574b4a0a0d5b13a48c48f3976b32"}]}
{"actor":{"display_login":"sadsfae"}}