)]}'
{"nova/scheduler/client/report.py":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"6a9eb8d66f91b067c696f123f408c46df137b313","unresolved":false,"context_lines":[{"line_number":1829,"context_line":"            raise exception.AllocationUpdateFailed("},{"line_number":1830,"context_line":"                consumer_uuid\u003dconsumer_uuid,"},{"line_number":1831,"context_line":"                error\u003d_(\u0027Cannot PUT empty allocations. \u0027"},{"line_number":1832,"context_line":"                        \u0027Did you mean to delete?\u0027))"},{"line_number":1833,"context_line":"        return r.status_code \u003d\u003d 204"},{"line_number":1834,"context_line":""},{"line_number":1835,"context_line":"    def _put_allocations("}],"source_content_type":"text/x-python","patch_set":1,"id":"5fc1f717_e3f9cdc7","line":1832,"updated":"2019-03-13 21:43:00.000000000","message":"Why can\u0027t we just check `not current_allocs[\u0027allocations\u0027]` and raise before attempting to _put_allocations? Does PUTting empty allocations sometimes work?","commit_id":"a8eec9824b26bd9bcaec37d79b7070a3a4d9e198"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"95dfed298eedd0c9969b7851a5e36d11c4297e5d","unresolved":false,"context_lines":[{"line_number":1829,"context_line":"            raise exception.AllocationUpdateFailed("},{"line_number":1830,"context_line":"                consumer_uuid\u003dconsumer_uuid,"},{"line_number":1831,"context_line":"                error\u003d_(\u0027Cannot PUT empty allocations. \u0027"},{"line_number":1832,"context_line":"                        \u0027Did you mean to delete?\u0027))"},{"line_number":1833,"context_line":"        return r.status_code \u003d\u003d 204"},{"line_number":1834,"context_line":""},{"line_number":1835,"context_line":"    def _put_allocations("}],"source_content_type":"text/x-python","patch_set":1,"id":"ffb9cba7_b2f6ebf8","line":1832,"in_reply_to":"5fc1f717_e3f9cdc7","updated":"2019-04-26 18:46:33.000000000","message":"\u003e Why can\u0027t we just check `not current_allocs[\u0027allocations\u0027]` and\n \u003e raise before attempting to _put_allocations?\n\nYeah I suppose we could, didn\u0027t think about it for whatever reason - I was focused on the 400 response I guess.\n\n\u003e Does PUTting empty allocations sometimes work?\n\nNo placement doesn\u0027t allow that.","commit_id":"a8eec9824b26bd9bcaec37d79b7070a3a4d9e198"}]}