)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"fd50a6b322d812d7da9438a706c0f7860044e2b2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8a1417ca_72f6e149","updated":"2024-01-30 09:52:44.000000000","message":"Thank you Yadnesh. This is a good catch!","commit_id":"41d43333b9bd48a804a3f3a461696756702cd72f"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"111675a71572bc481e7b7a149f1cd95819447b4a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cc4fafc4_2737dc61","updated":"2024-01-30 10:44:54.000000000","message":"The pep8 failure looks real.\n\nAlso, my understanding is that HashRing is used to distribute tasks among workers. So if there are different versions of aodh running in a single cluster, for example in the middle of upgrade from N to N+1, this may result in inappropriate partitioning. Probably we should at least document the upgrade impact, or probably we can even add an option to select the hash method ?","commit_id":"41d43333b9bd48a804a3f3a461696756702cd72f"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"f48644d5f169081c9fa178f6ba5d7da88f5cd8c1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a473b7a3_6b823ee5","in_reply_to":"cc4fafc4_2737dc61","updated":"2024-01-31 08:00:05.000000000","message":"https://review.opendev.org/c/openstack/aodh/+/907296 is probably a better approach","commit_id":"41d43333b9bd48a804a3f3a461696756702cd72f"}]}