{"push_id":1380215932,"size":1,"distinct_size":1,"ref":"refs/heads/dev/BF/handle_undefined_values_listMPU","head":"68a3fc6ca4de329f93837777e1cc2e57adcdb774","before":"eae648accbd8316fbe389d217f02beb825d73b58","commits":[{"sha":"68a3fc6ca4de329f93837777e1cc2e57adcdb774","author":{"name":"Bennett Buchanan","email":"1640784e29b5e19a149b9c0193e4b0cc8237fb02@scality.com"},"message":"BF: Fix `undefined` values for listMultipartUploads API\n\nThis commit fixes issues that were causing listMultipartUploads\nto contain 'undefined' as XML content:\n* `services.getMultipartUploadListing` in listMultipartUploads.js is\n  passing an `undefined` DisplayName for the owner of the MPU and\n  an `undefined` StorageClass for an upload. This results in the\n  following JSON response for the listMultipartUploads API,\n  respectively:\n\n  ```javascript\n  \"Owner\": { \"DisplayName\": \"undefined\", ... }\n  \"Uploads\": [{ ... \"StorageClass\": \"undefined\", ... }]\n\n  ```\n* Changes in getMultipartUploadListing.js fixes the\n  issues stated in the above bullet point by retrieving the proper\n  values for the keys `DisplayName` and `StorageClass`\n* For values that could be `undefined` in the listMultipartUploads\n  API, use empty XML elements if the value is, in fact, `undefined`\n* Add a test that compares the entire expected object, and remove\n  legacy 'list ongoing multipart uploads' tests which would\n  be redundant with this commit","distinct":true,"url":"https://api.github.com/repos/scality/S3/commits/68a3fc6ca4de329f93837777e1cc2e57adcdb774"}]}
{"actor":{"display_login":"bennettbuchanan"}}