)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"a331523543430334f7d0be26632555cd15caaf73","unresolved":true,"context_lines":[{"line_number":5,"context_line":"CommitDate: 2020-11-03 08:59:30 +0800"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fix hacking min version to 3.2.0"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"flake8 new release 3.8.0 added new checks and gate pep8"},{"line_number":10,"context_line":"job start failing. hacking 3.0.1 fix the pinning of flake8 to"},{"line_number":11,"context_line":"avoid bringing in a new version with new checks."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Though it is fixed in latest hacking but 2.0 and 3.0 has cap for"},{"line_number":14,"context_line":"flake8 as \u003c4.0.0 which mean flake8 new version 3.9.0 can also"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"8d58c9c2_ad539a18","line":11,"range":{"start_line":8,"start_character":0,"end_line":11,"end_character":48},"updated":"2021-02-28 02:32:01.000000000","message":"I cannot understand why the hacking min version to 3.2.0 while reading this paragraph.\nI am not against bumping the hacking version, but the description should match what happens.\nHonestly I don\u0027t see any flake8 failuree in openstack-zuul-jobs with flake8 3.8.x.","commit_id":"a4bc0961f6a6e4e27cfe37727883208c152fa51d"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"d889af381f0175c0f54f5cfaffb5075a8c1c541e","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fix hacking min version to 4.0.0"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"flake8 new release 3.8.0 added new checks and gate pep8"},{"line_number":10,"context_line":"job start failing. hacking 3.0.1 fix the pinning of flake8 to"},{"line_number":11,"context_line":"avoid bringing in a new version with new checks."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Though it is fixed in latest hacking but 2.0 and 3.0 has cap for"},{"line_number":14,"context_line":"flake8 as \u003c4.0.0 which mean flake8 new version 3.9.0 can also"},{"line_number":15,"context_line":"break the pep8 job if new check are added."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"To avoid similar gate break in future, and hacking 4.0.0 is available,"},{"line_number":18,"context_line":"we need to bump the hacking min version."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html"},{"line_number":21,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"5c88087f_eb0c829d","line":18,"range":{"start_line":9,"start_character":0,"end_line":18,"end_character":40},"updated":"2021-03-01 09:14:21.000000000","message":"I am reposting my comment in the previous patch set again. I still cannot understand these parargaphs.\nHow is it related to the situation we need to bump hacking to \u003e\u003d4.0.0?\nI don\u0027t see no failure in this repo, so I cannot understand this description.","commit_id":"9b0c52ce51c9542301085f0561866ab9e77bbc2c"}],"test-requirements.txt":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"42709f13711b2c07f109566094814c326d6badf3","unresolved":false,"context_lines":[{"line_number":2,"context_line":"# of appearance. Changing the order has an impact on the overall integration"},{"line_number":3,"context_line":"# process, which may cause wedges in the gate later."},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"hacking\u003e\u003d3.0,\u003c3.1.0 # Apache-2.0"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"# ansible-lint requires ansible\u003e\u003d2.9"},{"line_number":8,"context_line":"ansible\u003e\u003d2.9.0,\u003c2.10"}],"source_content_type":"text/plain","patch_set":3,"id":"1f621f24_04602401","side":"PARENT","line":5,"range":{"start_line":5,"start_character":12,"end_line":5,"end_character":20},"updated":"2020-11-02 15:37:48.000000000","message":"Keep hacking limited to 3.2.x - leave the upper cap in.","commit_id":"885e48c1b64e27373a880a3ad0e3a3649a388f5e"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"a331523543430334f7d0be26632555cd15caaf73","unresolved":true,"context_lines":[{"line_number":2,"context_line":"# of appearance. Changing the order has an impact on the overall integration"},{"line_number":3,"context_line":"# process, which may cause wedges in the gate later."},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"hacking\u003e\u003d3.2.0,\u003c3.3.0 # Apache-2.0"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"ansible\u003e\u003d2.7.0,\u003c2.8"},{"line_number":8,"context_line":"ansible-lint\u003e\u003d4,\u003c\u003d5"}],"source_content_type":"text/plain","patch_set":4,"id":"75d0ed61_cbab4c5e","line":5,"updated":"2021-02-28 02:32:01.000000000","message":"hacking 4.0.0 is available. I don\u0027t see a good reason not to use the latest version if you bump the hacking version.","commit_id":"a4bc0961f6a6e4e27cfe37727883208c152fa51d"}]}