)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"7dcf8e2dfd124b528dc1eae66022c24b02e81d5a","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Remove reported_enqueue flag from queue item"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"It seems that we check for the reported_enqueue flag only when"},{"line_number":10,"context_line":"initially enqueueing an item. This we can remove it and save a"},{"line_number":11,"context_line":"zookeeper operation when enqueueing a change."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: Ic869698e882377217410ea66825c5c999f9ae322"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f983fc3_57b7dc06","line":10,"range":{"start_line":9,"start_character":0,"end_line":10,"end_character":29},"updated":"2021-11-17 19:23:38.000000000","message":"And it isn\u0027t possible for addChange to be executed again because a single scheduler at a time is processing events for a pipeline. And when the event is pulled off we never put it back again to be processed by another scheduler in the vent of a failure? Basically we either process it here and we\u0027re good or we don\u0027t and move on?","commit_id":"92bbc2fe02423bdfece2c63d80f87c5a44544532"},{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"a7b66df96c66c2cc8f7e124551d7008ecad93944","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Remove reported_enqueue flag from queue item"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"It seems that we check for the reported_enqueue flag only when"},{"line_number":10,"context_line":"initially enqueueing an item. This we can remove it and save a"},{"line_number":11,"context_line":"zookeeper operation when enqueueing a change."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: Ic869698e882377217410ea66825c5c999f9ae322"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"08ac39d1_c1763def","line":10,"updated":"2021-11-17 19:54:18.000000000","message":"Exactly; the trigger event queue is a try/finally:\nhttps://opendev.org/zuul/zuul/src/branch/master/zuul/scheduler.py#L1872\n\nIt may be possible to have some ZK error that causes us to report enqueued and then fail to remove the event; however, we try almost indefinitely to write the pipeline state to ZK before we leave queue processing, so that is unlikely.","commit_id":"92bbc2fe02423bdfece2c63d80f87c5a44544532"}]}
