)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"19cf5eca2121677e5f1b3ed9c0cdb5150e5d63d1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c44a7dc7_29dba107","updated":"2026-11-09 06:28:22.000000000","message":"I\u0027ve made this change depend on 1014685. Could you include the change to remove handling of null evaluate_timestamp in this, because the logic may no longer needed after deployment is properly updated with the new migration script ?","commit_id":"7bc065f89a66edd7cffa452f7c7efdbca531458c"},{"author":{"_account_id":39493,"name":"Daniel Gines","display_name":"Daniel Gines","email":"dangines@gmail.com","username":"danielgines"},"change_message_id":"c8a2e84586321474fd3a65b2ab72b255907b5076","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"25eb96ad_55664260","in_reply_to":"c44a7dc7_29dba107","updated":"2026-11-09 18:13:09.000000000","message":"Done in PS3. This change now also removes the handling of a NULL evaluate_timestamp added by 1014685 from the evaluator: the second query in _assigned_alarms() and the conditional update of the NULL value in _evaluate_alarm(), with their tests. After the migration no alarm has a NULL or future evaluate_timestamp. I kept the fallback to the current time on PUT: during a rolling upgrade an old aodh-api can still store NULL after the migration ran, and without the fallback such an alarm would never be evaluated again. The release note now says that aodh-dbsync must be run before the upgraded evaluator is started. I left the column nullable to keep this change free of schema changes; I can make it NOT NULL in a follow-up if you prefer.","commit_id":"7bc065f89a66edd7cffa452f7c7efdbca531458c"}]}