)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3f971579d2a20c28c25d64022fe426d5ed741270","unresolved":false,"context_lines":[{"line_number":13,"context_line":"didn\u0027t respect the limit set by CONF.osapi_max_limit. The only"},{"line_number":14,"context_line":"concrete example of this was images. This patch modifies"},{"line_number":15,"context_line":"get_pagination_params to bring it in line with its own docstring. This"},{"line_number":16,"context_line":"also has the nice side effect of fixing images\u0027s pagination."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"APIImpact"},{"line_number":19,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"1a4dcd0f_9401dab1","line":16,"updated":"2015-08-05 14:13:12.000000000","message":"This seems back to front, the important thing about the API is its current behaviour. We shouldn\u0027t change the API to match a doc string, we should update the bad doc string.\n\nAlthough I do actually like this extra protection this gives nova-api when proxying through to glance.\n\nPlease change this into a commit and bug that looks at ensuring Nova users CONF.osapi_max_limit when proxying calls to glance.","commit_id":"82aa3098b3723db2a20e9436a1d55e31a09c3eab"}]}