{"push_id":600226800,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"0b906705a2414cb6cfbdf8935660f02f788e3fa3","before":"148d60e4f9fd04b109dccb39305f012f2339a038","commits":[{"sha":"0b906705a2414cb6cfbdf8935660f02f788e3fa3","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Updated openstack/openstack\nProject: openstack/cinder  74d2385854cbf82c6d903b1a4ff4fab1fdfd6289\n\nRemove the useless next link for volumes, transfers and backups\n\nTwo cases this patch will resolve:\n1) Currently if the number of items equals the osapi_max_limit or\nthe last page of items equals the osapi_max_limit without the\nparameter limit set in the user request, a next link is generated\nin the response, though this next link will return empty volume\nlist. In fact it is unnecessary to generate the next link in\nthis case.\n\n2) If the number of items equals the osapi_max_limit and limit is\ngreater than osapi_max_limit, a next link is generated. Actually,\nthe next link does not need to be generated, because it is certain\nthat there is no more volumes left in the database.\n\nThe method _get_collection_links has been called in volumes,\nvolume_transfers and backups. The patch can only affect the next\nlink generation for three of them. However, other lists like\nconsistency groups, qos specs, cgsnapshots have not implemented the\ngeneration for the next link. Potentially this can be a wishlist\nitem for them.\n\nChange-Id: I0f1f449c73d51675281497a095d869c1e72c889f\ncloses-bug: #1350558","distinct":true,"url":"https://api.github.com/repos/openstack/openstack/commits/0b906705a2414cb6cfbdf8935660f02f788e3fa3"}]}