)]}'
{"openstack_dashboard/test/helpers.py":[{"author":{"_account_id":8648,"name":"Radomir Dopieralski","email":"openstack@dopieralski.pl","username":"thesheep"},"change_message_id":"988fdf730f7f89a39c34fbc920befca48ce444f0","unresolved":true,"context_lines":[{"line_number":440,"context_line":"        else:"},{"line_number":441,"context_line":"            _expected \u003d expected_msg"},{"line_number":442,"context_line":"        self.assertIn(_expected, messages)"},{"line_number":443,"context_line":""},{"line_number":444,"context_line":""},{"line_number":445,"context_line":"class BaseAdminViewTests(TestCase):"},{"line_number":446,"context_line":"    \"\"\"Sets an active user with the \"admin\" role."}],"source_content_type":"text/x-python","patch_set":2,"id":"addf3849_37ec8d39","line":443,"updated":"2021-09-14 12:36:06.000000000","message":"Should we also change it where the messages are actually used?","commit_id":"84648cb371beeb0e71ca58f67bf483390e7d6765"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"0d0295e54b1c6baafb3d36f6928679ecfefd2089","unresolved":true,"context_lines":[{"line_number":440,"context_line":"        else:"},{"line_number":441,"context_line":"            _expected \u003d expected_msg"},{"line_number":442,"context_line":"        self.assertIn(_expected, messages)"},{"line_number":443,"context_line":""},{"line_number":444,"context_line":""},{"line_number":445,"context_line":"class BaseAdminViewTests(TestCase):"},{"line_number":446,"context_line":"    \"\"\"Sets an active user with the \"admin\" role."}],"source_content_type":"text/x-python","patch_set":2,"id":"430e7037_c6c314a0","line":443,"in_reply_to":"addf3849_37ec8d39","updated":"2021-09-16 09:57:03.000000000","message":"In my understanding, the actual code uses Django message mechanism, so I think we don\u0027t need to change where the message are actually used. It is covered by the Django code. \nOn the other hand, the test code touched here accessed to the stored cookie directly, so such tests start to fail with Django 3.2. This is what this commit would like to address.","commit_id":"84648cb371beeb0e71ca58f67bf483390e7d6765"}]}